> However, I'm still of the view that trying to reproduce with a non-distro JDK > build is useful. I've had distro builds that behave differently, crash in > odd places, and even manage to run more than one EDT at the same time.
Ah, OK. I can see that it would be ideal to see thread dumps with the crash from a "vanilla" OpenJDK or Zulu distribution. Whenever I see an intermittent bug like this, though, my instinct is to avoid changing my configuration, in case the bug stops being reproducible. Then I will never know what caused it, or when it will return... -- Eirik -----Original Message----- From: Neil C Smith <[email protected]> Sent: Wednesday, August 11, 2021 4:25 PM To: dev <[email protected]> Subject: Re: How to diagnose lock up with 12.5 Beta 1 On Wed, 11 Aug 2021 at 15:09, Eirik Bakke <[email protected]> wrote: > > But if the problem goes away with a different JDK, that doesn't mean the bug > is in the JDK--it just means the bug cannot be reproduced. > > For example, if two different NetBeans threads acquire nested locks in > opposite order, that would be a deadlock bug- True, and pointed out one possible sign of that happening already. However, I'm still of the view that trying to reproduce with a non-distro JDK build is useful. I've had distro builds that behave differently, crash in odd places, and even manage to run more than one EDT at the same time. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
