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.
Some types of watches take a very long time to update. I'm running on Win2000, 750Mhz, 256Mb. Attached is a program that demonstrates the problem. (This a program from my daughter's CS class, you'll have to change the input filenames and put a bit of data in them.) Set bps on lines 22 and 29 and do a watch on "dis". Run until control hits the one on line 29. Then do a restart. It takes nearly 30 seconds after the bp is hit before the watch window is updated with dis = >identifier cannot be resolved: dis< during this time the CPU is at 100%. The CPU remains at 100% for close to another 25 seconds.
Created attachment 5319 [details] Test Case
I can not reproduce it on my machine (WinNT, JDK1.4.0-beta3). Can you attach info about your JDK and ide.log, please? It can be caused by potential memory leak - can you test it with fresh netbeans session (first debugging after netbeans ide start), please? - we have high level goal to improve runtime performace for NetBeans3.4, and I plan to do some more advanced performace testing to find such performace problems. Thanks for your time.
Target milestone was changed from '3.4' to TBD.
I am experiencing a similar problem. It also seems related to watches. I've experience the same long wait of 100% CPU load. Even worst it is followed by irratic behaivor: wrong results of simple function calls. Also the debugger continued by itself (was stopped at a breakpoint) after a tooltip watch. This was on NB3.3.2, Windows XP, JDK1.3.1 AND JDK1.4.0. I am unable to reproduce the problem on another computer NB3.3.2, Win2K, JDK1.3.1. Maybe theres a bug in the VM? The log shows no indication of anything ever going wrong
Should be fixed in release35
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.