Repository navigation
The project tree expanded/collapsed state is randomly honored or not between launches #9657
Description
Apache NetBeans version
Apache NetBeans 31
What happened
As I close and restart Netbeans, the project tree randomly collapses and expands random nodes.
Language / Project Type / NetBeans Component
Java Maven
How to reproduce
Open a project
Expand the project folders and packages
Do some work
Close Netbeans
Relaunch and reopen the same project. 1/2 of the time the tree will be in a different, random state
Did this work correctly in an earlier version?
No / Don't know
Operating System
Linux
JDK
21
Apache NetBeans packaging
Apache NetBeans binary zip
Anything else
No response
Are you willing to submit a pull request?
No
Activity
dca00 commentedon Oct 4, 2026
And sometimes it stays at this state indefinitely. My gut feeling is that the amount of time that passed since Netbeans was last closed is proportional to the probability of this happening, but this is inconclusive:
neilcsmith-net commentedon Oct 5, 2026
The failure to get beyond
Initializing project...is something of a known issue, although rarely seen. I discussed on Slack with @mbien a while back. I see it far more in a platform application, where the module graph and projects themselves are lighter and quicker to load, which makes me think it's a race condition somewhere. It seems to be that the project gets loaded and turned back into aLazyProject. I have a log trace that shows this happening.mbien commentedon Oct 5, 2026
the "Initializing project" bug sometimes happened to me while testing when the action triggers cluster activation. I don't think I ever encountered it during regular ide use when I opened a project or switched groups etc (and the java cluster was already active).