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.
Steps: 1. Start IDE (assuming more than one project was opened in the Project Window at the previous shutdown) 2. Observe that at the bottom of the IDE, a progress type indicator states that the IDE is scanning one of the projects 3. Go to the Project Window and close the project being scanned 4. Observe that the IDE continues to scan the project even after it has been closed The problem is that given all my projects are large (3 VCS modules within each project, with approx. 1000 files total per project), the scanning takes up time and process overhead. When I need to do a "Go To Type", nothing displays until the scanning process is done. I don't want it to scan the project that has been closed. This results in poor performance.
The scanner process events classpath changes in synchronous way. It is not able to find out if the classpath change is caused by closing project or something else.
*** Issue 131651 has been marked as a duplicate of this issue. ***
Please fix this. My computer has been racing ( and I have been unable to even bring up a popup menu in NB ) for a minute now because it is scanning a closed project. I am not doing anything to those files, so I have no idea why it decided to scan them now, but I do know I have to wait for it. I have been a faithful NB supporter for years, but I am seriously considering looking at alternatives...even though I know porting the projects and learning a new IDE would be a big deal. I think I spent at least 15 - 20 minutes just waiting on NB to scan. My computer is not the newest in the world, but it is not bad (2.8 GHz P4 with 1.25 GB of memory) Please NB, at least schedule a fix for this in 6.5. If I was a trial user and experienced these waits, there is no way I would even consider it. Help me out here...I want to be an enthusiastic supporter of NB again!
Can you add sore details how the IDE started to scan the closed project? Was it caused by closing the project? Was there a project depending on the closed project? Thanks
I will keep a look out for when it does the autocompile. Today it seemed that closing the project caused it. I had to switch to another project to fix something. I closed the current one (in a state of disarray, I might add), and then open the other one. When it started opening the new one, I noticed it compile the previous one. I can't say for certain that it was not auto-compiling before I closed it though. I guess a corollary to this bug would be that it would stop auto-compiling a project when it is closed. I basically have a project per release. Each release has a few different projects, but I rarely open any but the main one for each release. (At some point I want to re-arrange my source tree, but until we start using SVN I am not going to move stuff around to more effectively utilize the project structure.) So, to answer your question, "No, these projects do not depend on each other."
Yes, this totally just happened. I have had both projects A and B open. These projects are completely separate (they where checked out from CVS into different working directories). This is what just happened: Project B was open and at rest. I closed Project B Pause I opened Project A Project A started to open Auto compile of project B
This time I was sure that it was not scanning a project and when I closed it, it started scanning. I waited for it to stop, opened another project, and is scanned the new project this time (not the old one).
Happened again. It closed fine, but the minute I opened the menu to open a recent project, boom, scan the closed one. These are long scans too. They take several minutes ( about 2700 source files ), this one is probably taking at least 5. Granted, there are competing jobs for the disk and CPU. However for this 5 - 10 minutes, NB is pretty much useless to me. There are several third party jars in the project, but by looking at the status bar, these take basically no time if it scans them at all.
Now it happened in a different way. I believe it was quiet when I clicked the toolbar button to debug my project. It asked me to select a main project, I did, and then I had to wait for a different project to be scanned before I could start my debugging session. Then the little dialog telling me to wait closed and it started scanning the project I was debugging. It waited for that to complete before the debugger started, although there was no dialog. Again, another couple of minutes just waiting for NB to come around. I think I have ranted enough on this to get my point across, and will refrain from more posts unless I believe I have something more useful to add. I spend at least 10-20 minutes each day directly waiting for NB to come around (like when trying to run a project). And probably quite a bit more than that in degradation of performance that occurs when it is scanning (the right project or not). The productivity lost because of scanning, especially that for closed projects, is becoming overwhelming. Please address these issues.
*** Issue 141178 has been marked as a duplicate of this issue. ***
*** Issue 120910 has been marked as a duplicate of this issue. ***
*** Issue 142361 has been marked as a duplicate of this issue. ***
I have to agree with mclaassen, we really waste considerable amount of time just waiting for the IDE to respond. It also seems that atleast 4 people have reported this issue. Please let us know what kind of help we can provide to have this resolved.
I opened this bug over a year ago.
*** This issue has been marked as a duplicate of 67025 ***