On Sat, Jul 14, 2018 at 10:39 AM Geertjan Wielenga <geertjan.wiele...@googlemail.com.invalid> wrote: > I hope you understand. We can’t create another whole new build and restart > voting from scratch at this stage, unless we as a community decide that this > is what must be done, delaying the release significantly. I do understand. Do you agree that there are two (probably independent) problems here, first the reflection warning, second the JVM crash? (I'm assuming this is reproducible for everyone?) The first is NETBEANS-298 and it is a warning that can be dealt with in a future release. The second is not Netbean's fault - as I understand it, it should not be possible to crash the JVM like this from Java code (correct me if I'm wrong!). Alan has reported this to Oracle and I will be interested to see the response. However, wherever the problem lies, the result is that NB's profiler doesn't work. Is there a JIRA issue filed on this? The community may decide this is a blocker but they can't judge that if there's no issue on record. Thanks as always for your help on this.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
