Quite regularly NetBeans starts being sluggish after some time it has started.
At irregular intervals of a few seconds NB freezes for a couple of seconds and does not accept any interaction.
It looks like there is something done in the background that grabs control of the UI.
It is very unnerving and time consuming.
I have made available the diagnostic files generated using VisualVM at the following locations:
At first I thought it was due to a very high number of unversioned files (several thousands) I had in my open projects but the problem did not disappear after deleting all of them.
I have come to think that the issue is caused by Windows running short of file handles.
My code was not calling resp.getEntity().consumeContent() (of class org.apache.http.HttpResponse)
Since the code was invoked thousands of times, Win XP ran out of handles (I think) and NB started to be sluggish.
However, I am still having the problem from time to time....
Very difficult to nail down, this one.
Now I am having the sluggish behaviour.
The only relevant thing is that I have the output window full with a lot of logging information.
I remember this being an issue also with output generated by Tomcat...
NetBeans IDE 7.0.1 build #201106020000
I have uploaded a new set of files.
(In reply to comment #5)
> NetBeans IDE 7.0.1 build #201106020000
> I have uploaded a new set of files.
There is nothing wrong in the application snapshot you provided.
There is no need to attach these separately. Thread dump and heap dump are already part of the application snapshot. If you need to upload heap dump for some reason please upload compressed version.
Got sluggish again, here is the snapshot:
If the snapshot is not showing anything, even though the ide IS terribly slow, please tell me how I can collect the information .
(In reply to comment #7)
> Got sluggish again, here is the snapshot:
> If the snapshot is not showing anything, even though the ide IS terribly slow,
> please tell me how I can collect the information .
According to the snapshot, it looks like a lot of time is spend GC. You can see it yourself in the monitoring tab. Heap dump shows a lot of data from the junit tests, Find usages and debugging session. It looks like your junit tests produce a lot of data and this could be a reason that the heap is almost full. I would suggest to increase Xmx to 480M and see if you can reproduce it. If you have a reproducible test case, it would be great to have it.
A huge number of files in the Windows temp directory might have been the cause.
Probably a duplicate of buf 212479
*** This bug has been marked as a duplicate of bug 212479 ***