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.
[ JDK VERSION : 1.5.0_02 ] I am running into serious performance problems with RC2 where the cpu is pegged for minutes at a time and the heap usage cycles from 80meg to 200+meg and then back again repeatedly. This all while I am doing nothing, not even editing! Unfortunately I can not easily repeat the problem. The project is quite small (20 files or so). I've attached two thread dumps while the cpu was heavily used by the IDE and the IDe log.
Created attachment 22011 [details] thread dump
Created attachment 22012 [details] IDE log
What is your hardware config? Is it possible that your system starts swapping? Then it might better to use lower -Xmx. Both dump are from javac parsing (and both are deep). It seems also that the user runs on Tiger but project uses 1.4.2. Reassigning to Java module.
I still do not know what can be the reason. Do you use network drives? What kind of activity leads to this problem? How can we reproduce it? user wrote: Hardware is 2Ghz P4 with 1 gig of Ram. No possible that this is swapping as I was running task monitor and there were no other significant applications running at the time. You are correct that the application is a 1.4 application while the IDE runs on 1.5.
This issue has been true since 4.0 was first released. Several folks have noted the same problem on various Windows configurations. Swapping doesn't appear to matter very much, nor does networked/clustered drives. Hardware speed does make a difference but only in how long the hang ups last. I've seen this situation last several minutes on slower systems. This looks to be related in some way to the syntax checker. Changing the "Automatic Parsing Delay" parameter (Options/Java Sources) to a large number (currently runing 20000) improves performance dramatically. NB 4.1 (200505031930) Windows 2000 SP4 JDK 1.5.0_02-b09
Can you reproduce this bug with latest trunk build?
> Can you reproduce this bug with latest trunk build? Answer from reporter: nope code long gone