What is the memory situation And CPU usage like? Perhaps the combination of NetBeans and Gradle daemon JVMs is consuming too many resources for some reason?
Scott > On Apr 3, 2020, at 3:01 PM, Rob Walker <[email protected]> wrote: > > > Yeah. Also agree it's unlikely NB alone. Definitely seems to need Java &Grade > & NB all running. Of those Java has most native code. Haven't ruled out some > narrow machine hardware or driver issue that this combo is tripping. Just not > see any evidence after a freeze that I can use to track it. Clutching a bit! > - Rob > > Sent from Outlook Mobile > From: Laszlo Kishalmi <[email protected]> > Sent: Friday, April 3, 2020 6:07:03 PM > To: [email protected] <[email protected]> > Subject: Re: Freeze/Crash of NB 11.3 on Windows - anyone else? > > It is unlikely that NetBeans does this alone. Most probably you are having an > underlaying hardware issue which is triggered by a certain load created by > using Java, Gradle, NetBeans. > > Years ago it turned out that I have a defected core on my CPU. The defect > could be caused during executing "massive" parallel computations, like Gradle > parallel builds. When it kicked in the system hanged. Fortunatelly Linux was > able to log out the core misbehavings as it happened a few times before the > hang, so I could made my system stable by disabling the faulty core. > >> On 4/3/20 1:50 AM, Rob Walker wrote: >> Been a 11.2 user for a while. Hard to isolate what I’m seeing down to be >> certain it is 11.3, but it started right after the upgrade, and only seems >> to happen when I am working with NB 11.3 >> >> What I get is not a Windows crash in the BSOD sense, but a complete and >> utter freeze of the system. Can’t even get to TaskMan via a Ctrl-Alt-Del – >> mouse moves still on screen, and I can occasionally select a window and see >> the title bar change color as it gets focus. But aside from that I am >> completely locked out. Power off button is only way to recover. >> >> Seems really odd that an IDE like NB could do this – do wonder if it isn’t >> NB solo but some collision between NB scanning dir changes, and me running >> Gradle manually outside of NB to do builds from command window. The only >> time I get this freeze so far is with both of those open. And I am also >> seeing a much greater occurrence of Gradle daemon process zombies since the >> 11.3 upgrade – which also makes me suspect that maybe either Gradle and NB >> are fighting, or maybe that newer Gradle 6.x builds are a factor here. >> >> Wondering if anyone else is seeing any kind of similar freeze?
