This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version = NetBeans IDE Dev (Build 201510180002) Operating System = Windows 7 version 6.1 running on amd64 Java; VM; Vendor = 1.8.0_60 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Reproducibility: Happens every time Today I installed latest nightly build; before I had 201510160002, and it was working without problem. After I launch NB, it starts, and is opening projects. And then, without doing nothing, it just freeze, and I can do nothing, even not close NB. To processor has for netbeans64.exe max load, and I can only end the process
Created attachment 156800 [details] IDE log
Can you create and attach a thread dump of the frozen NB instance? http://wiki.netbeans.org/GenerateThreadDump
Reopen if this happens again and you can provide the thread dump.
Right now its frozen, and it became unfrozen after many minutes, and showed Java error - Interrupted attempt to acquire write lock. Then I tried to send bug report, but it freeze again. If I success with this, I will attach here the bug ID.
(In reply to legitalk from comment #4) > If I success with this, I will attach here the bug ID. Plus reopen the bug again. Thanks!
(In reply to legitalk from comment #4) > Right now its frozen, and it became unfrozen after many minutes, and showed > Java error - Interrupted attempt to acquire write lock. > > Then I tried to send bug report, but it freeze again. If I success with > this, I will attach here the bug ID. Another bug report will not help. Just take the thread dump as requested above and attach to this issue.
I tried this, but there is no console windows. And also there is no nb.exe... Press Ctrl-Break in the command console you used to start the IDE If the console isn't opened (in case you started the IDE using the default desktop icon): launch the IDE using a console window (invoke Command Prompt, go to {netbeans-install-dir}/bin and type nb.exe) configure the desktop shortcut to launch the nb.exe instead of netbeans.exe (default) NB7 and later - there is no nb.exe, just run netbeans.exe from console. If NB is started by shortcut use "--console new" option to open console (netbeans.exe --console new). The thread dump is printed into the command console. Just assure that the console have the line buffer long enough so that the whole thread dump fits in.
Then simply use VisualVM [1]. It's very easy. [1] https://visualvm.java.net
Created attachment 156838 [details] Thread dump, when NB was frozen.
This thread dump is cut in the middle and it is also wrapped which makes reading very difficult. Can you please generate another one which would be correct? Thanks!
I setted up settings of cmd to 999 memory lines and etc, everything to maximum as possible and copied everything what was there.
Also btw. I found out how to solve this bug. NB was not usable anymore. When launched and it was opening projects, everytime it freeze in few minutes. But I deleted all nbproject folders in each project and then launched it again and there was no project. I created again all projects and there restart IDE a d the problem was fixed...
What a shame you didn't backup those project directories. We cannot reproduce it so I am marking this bug as WORKSFORME. Next time please really use VisualVM to generate the thread dump. Thanks!
Don't worry, yesterday this solution solved the bug. But today its happening again :-) So what you want from me now? Upload of project netbeans directories?
Created attachment 156898 [details] nbproject of two opened projects This two project I have since yesterday, and it was working; today morning its happening again, and when NB is opening that projects on start up, it freeze...
Great, can you please also install the VisualVM, generate the Full Thread Dump with it and attach it here? Thanks!
When I used VisualVM, this is happening: - NB is running much more slowly - the problem is not occuring When I dont use VisualVM, the problem is happening... So?
*** Bug 256077 has been marked as a duplicate of this bug. ***
Created attachment 157035 [details] Thread dump, when NB was frozen. Ok, so finally a did it. The problem was, when NB and VisualVM were running together, NB was running approx. 50% slower... So I started only NB, there were 3 projects opening, after couple minutes it was frozen, as always, so NB was again as always not usable. Then I launch VisualVM, and do thread dump. Hope now it helps you somehow.
And as I said before, when NB and VisualVM were running together, this bug wont happend...
I went through the changes between build #201510160002 and build #201510180002 and did not find anything that seems to be relevant to this deadlock. Can you please check build #201510170002 at http://bits.netbeans.org/download/trunk/nightly/2015-10-17_00-02-28/ ? Also, can you please check the latest trunk build, just for the case that build #201510180002 happens to be corrupted for some reason? Also, is the 8.1RC2 working fine for you? http://download.netbeans.org/netbeans/8.1/rc2/ Thank you.
Its still happening in the latest build #201510290002. And now its happening also in #201510160002, so I really dont know, when it started :-/
In thread "AWT-EventQueue-0" #21, DefaultMutexImplementation read mutex is acquired, PHP project is trying to get the list of problems for the node's display name and thus it starts lookup for the providers. This lookup waits for a notification from another thread (most probably "org.netbeans.spi.project.ui.support.NodeFactorySupport" #78) Thread "org.netbeans.spi.project.ui.support.NodeFactorySupport" #78 is collecting a lookup of all important files (ImportantFilesImpl.getAllInstances()) and as a result of such collection, ImportantFilesImpl.resultChanged() is called. As a response to this lookup change, ImportantFiles$ImportantFilesChildren calls setKeys(), which tries to acquire write mutex from DefaultMutexImplementation. But this can not be accomplished, since read mutex is already held by "AWT-EventQueue-0".
Moving to PHP for evaluation. Perhaps ImportantFilesImpl could be adjusted to e.g. ignore the lookup changes during collection of the instances? Unfortunately, LazyLookupProviders set the lookup content on query.
@jhavlin: Jardo, isn't it the same as issue #253732? Thanks.
(In reply to Tomas Mysik from comment #25) > @jhavlin: Jardo, isn't it the same as issue #253732? Thanks. Unfortunately, I wouldn't say so. It may be related to that issue, but I think it should be fixed separately. (Reporter uses build 201510180002, which should already contain fix for the issue.) > Perhaps ImportantFilesImpl could be adjusted to e.g. ignore the lookup > changes during collection of the instances? This would be nice.
In the latest nightly build #201511020002 (x64) it is still present, and NB freeze during opening projects (I have 2 projects in projects windows). I just downloaded and installed the oldest available nightly build #201510030002 (x64), and there it is also happening. Then I downloaded and installed 8.1rc2 (x64), and also copied AppData\Roaming\NetBeans\dev to \AppData\Roaming\NetBeans\8.1rc2 and the same with \AppData\Local\NetBeans\Cache\dev to \AppData\Local\NetBeans\Cache\8.1rc2, and it is still happening. So now I am thinking, maybe there is some problems with stored appdata files. I finally downloaded and installed 8.0.2 (there was no choice of x64 or x86), where for sure I didnt have this problem with NB freezing after start some weeks ago, when I was using this version, and here I also copied that all AppData files, and here to problem doesnt exists. So the problem is not with my AppData files, and it should be something like is mentioned in comment #23 by Martin Entlicher. So the problem is occured in 8.1rc2 and also in #201510030002, but its not in 8.0.2. Hope this analysis helps you. Thanks.
@legitalk: You can always try a clean userdir [1] (without importing the old one, just to be sure). Thanks for reporting. [1] http://wiki.netbeans.org/FaqAlternateUserdir
(In reply to Tomas Mysik from comment #28) > @legitalk: You can always try a clean userdir [1] (without importing the old > one, just to be sure). > > Thanks for reporting. > [1] http://wiki.netbeans.org/FaqAlternateUserdir Yes, thanks, but there is not mentioned 8.x (Applies to: NetBeans 3.6, 4.x, 5.x, 6.x, 7.0, 7.1), so I was not sure, if I can do this. Also I tried this bug on clean userdir, then I created again that two projects, and later it freeze again after restarting NB IDE.
Should be fixed now we hope. Please, wait for a comment saying in which dev build the fix will be present and test it. If the problem still exists, reopen this issue and attach a new thread dump. Thanks Jardo for your help. http://hg.netbeans.org/web-main/rev/0f7329c98965
Ok, thanks. I will wait for info about DEV build, in which it will be present. Till then I am using 8.0.2, in which this bug is not present; but I am strugling with another bug - 248481 - Really slow ftp upload, which is present in 8.0.2, but fixed in newer versions... Hope you can publish it ASAP. Thanks.
Integrated into 'main-silver', will be available in build *201511040002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/0f7329c98965 User: Tomas Mysik <tmysik@netbeans.org> Log: #256017 - NB freeze after start
Tested and looks like now its working and not freezing. Thanks. Great work!
(In reply to legitalk from comment #33) > Tested and looks like now its working and not freezing. Thanks. Great work! Thanks for verification.
Transplanted to release81 branch of releases repo: http://hg.netbeans.org/releases/rev/3084344fc691 http://hg.netbeans.org/releases/rev/31f54a9a4fd6 Please verify, if possible. Thanks.
legitalk can you please verify this issue one more time? this time in 8.1patch1. The patch process is described at page http://wiki.netbeans.org/NetBeans_81_Patch1_GoNoGo in section "Upgrade from 8.1 to Patch 1 sanity test" Thanks