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.
Created attachment 132060 [details] IDE Log Using NetBeans DEV 201302272300 on Windows 7 x64 with JDK 1.7.0_13 x64. Right click a subfolder in a project, then choose "find...". Find dialog is shown, user fill the word to search for and click Find. NetBeans got frozen, not saved code is lost. Not recoverable, has to go into Task manager and kill the netbeans64.exe process to start again. Attached there is: - NetBeans log - Screenshot - Thread dump from Visual VM
Created attachment 132061 [details] Screenshot of the issue
Created attachment 132062 [details] Thread dump
nothing project specific in the stacktraces, reassigning to search subcomponent for evaluation
Can you reproduce the bug? Is the IDE frozen every time you run the same search? Is is frozen if you search in another directory? Is there a lot of matches when the search is completed? Thank you.
(In reply to comment #4) > Can you reproduce the bug? I don't know the cause, so I can assert I can reproduce. I've not analyzed the stack trace, but I do suspect it is related to other filesystem freeze I've experienced sporadically. My bets are on a lock in Object at jvm low level... > Is the IDE frozen every time you run the same search? No. Actually, I've never faced this issue before - but since I'm using DEV, would a newly introduced bug caused by fix in other areas (for instance, the new find interface/result modes?). > Is is frozen if you search in another directory? No. > Is there a lot of matches when the search is completed? No. About 12. > Thank you.
Thread org.netbeans.modules.csl.navigation.ClassMemberPanelUI seems to call org.netbeans.modules.parsing.api.ParserManager.parse() while it holds Children lock and prevents other threads from updating node hierarchy. Reassigning to Editor/CSL. Can you please check it? Thank you.
This will be fixed by fixing #225925 *** This bug has been marked as a duplicate of bug 225925 ***