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.
I experience such behavior quite often: after restart of the IDE some projects stays in the "initializing..." state, I can not do anything with them except close and open them again.
Can you please capture thread dump?
Created attachment 86518 [details] stacktrace
sure, I attached the stacktrace
I'm not sure but I experienced this behavior after I tried context menu on some projects right after the IDE start, the menu contained only "intitializing" and "close" items and never changed to the regular type after that.
Seems to be a race condition in Jarda's lazy projects. Reassigning to Jarda
The stack trace is not really useful. I guess I need $userdir/var/log/messages.log file. Please attach it when you experience the problem again.
it is easy because I experience it every day! Please raise the priority back.
Created attachment 86526 [details] messages1
The messages.log contains tons of messages and exceptions (there are failures in editor, classpath, debugger, versioning), but none of them seems to be related to lazy project opening. If you can reproduce easily, then please simulate the problem with -J-Dorg.netbeans.modules.project.ui.OpenProjectList.level=ALL and attach the messages.log again. Thanks.
Created attachment 86527 [details] new log
see new log attached, I did not check all opened projects but: C/C++ Remote Development API (cnd.api.remote) C/C++ Project Bridge (cnd.api.project) are stuck in initialization for sure
Looks like you can reproduce the problem quite easily.
There is something wrong with directories: FINER [org.netbeans.modules.project.ui.OpenProjectList]: replacing for org.netbeans.modules.project.ui.ProjectsRootNode$BadgingNode@b5922e[Name=file:/export/work/cnd-main/cnd.api.project/, displayName=C/C++ Project Bridge] FINE [org.netbeans.modules.project.ui.OpenProjectList]: wrong directories. current: /export/work/cnd-main/cnd.api.project new /export/work/cnd-main/dlight.threadmap.support
Jardo, any progress on resolving this issue?
I will try to reproduce the problem locally, but I cannot open all your projects. You seem to have not only NetBeans.org Hg projects, but more: SuiteProject[/export/work/toolshg/dbxgui/dbxguisuite SuiteProject[/export/work/toolshg/dbxgui/Dbxtool FreeformProject[/export/work/dbx_libs/latest/t-common NbModuleProject[/export/work/toolshg/dbxgui/sunstudio.base FreeformProject[/export/work/cnd-main/nbbuild NbModuleProject[/export/work/toolshg/dbxgui/sunstudio.glue J2SEProject[/home/eu155513/NetBeansProjects/jsch141 SuiteProject[/export/work/toolshg/dbxgui/dbxidesuite NbModuleProject[/export/work/toolshg/dbxgui/dbxfacade.ide NbModuleProject[/export/work/toolshg/sside/core MakeProject[/export/work/dbx_libs/latest/dbx/dev/src NbModuleProject[/export/work/toolshg/dbxgui/dbxfacade.tool NbModuleProject[/export/work/toolshg/dbxgui/sunstudio.lisp NbModuleProject[/export/work/toolshg/dbxgui/dbxgui Maybe the problem is in one of those. Can you close these and try to reproduce just with NetBeans.org projects?
Created attachment 87751 [details] Just opening these projects seem to work
Closing extra projects does not help: - I closed the specified projects - restarted the IDE - tried to expand different projects in the projects view result is the same - some of them ~30% became "Initializing" forever. I can run it with any flags needed and provide any extra information needed. It is really disturbing.
another thing that came into my mind: sometimes I closed the IDE before complete parsing of the projects was finished, may that be the case?
I also closed the IDE before parsing finished and it worked for me. Parsing shall not affect state of the projects. I'll dig into it more.
Are you running with assertions enabled or disabled? I guess disabled. Enable them and the failure disappears. If so, I know what to fix.
If the cause was disabled assertions, then it is fixed in core-main#2e832ebf0235
yes, I'm using release version with assertions disabled, with enabled assertions I'm unable to reproduce it. Thanks!
Thank you for pushing me to fix the problem. Nobody could not reproduce it locally as people I asked were running the recent dev builds and those have assertions on. This was dangerous bug - fixed in dev builds, present in every release.
Integrated into 'main-golden', will be available in build *200909181401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/2e832ebf0235 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #170711: The project nodes need to be checked every time not only when running with -ea