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.
Every now and then, when I save a modified Java file in the editor (using Command+S), the IDE hangs for about 4 seconds before the file is successfully saved. During this time I get a busy mouse pointer, and nothing else can be clicked in the IDE. Since I save very often while editing code, this is a big annoyance even though it only happens maybe every 10 times. Unfortunately I haven't found a reliable way to reproduce the bug. I'm opening a bug in case others are experiencing the same problem and want to chime in. I'll comment on this bug with more information if I find out more or find a foolproof way to trigger the bug. I'm fairly certain this behavior is new in NetBeans 7.3--I didn't experience it before upgrading from 7.2. Note that I'm using MacOS and Java 1.6.0_43--not sure if that matters.
Could you please take a profile snapshot (through Profile Me feature) during the freeze, attach it here and reopen ? Thanks in advance. http://wiki.netbeans.org/GenerateThreadDump#Profile_Me_Now
Will do--thanks!
Created attachment 133772 [details] .npss file attached from NetBeans .npss file
Here's the requested snapshot. The freeze occurs for 6 seconds starting at 2:52:42.7 and can be clearly seen on the "stack depth" plot--it is constant at 136 for the whole duration of the freeze.
(Or rather, I suppose the stack depth isn't actually constant, but during the freeze, the profiler only managed to get a couple of samples.)
The problem is with apple.awt.CGlobalCursorManager.findHeavyweightUnderCursor[native]() 59.07514 3,812 ms (59.1%) 3,812 ms What is your jdk version?
This was under Java 6 on MacOS. I just yesterday upgraded to Java 7 and the latest development version of NetBeans--I can post another comment if I discover the bug there as well.
3 weeks without hearing about your jdk 7 version, seems to me It works well ^^ Reopen if not with snapshot, thanks
mkristofic@netbeans.org: Yes, in 3 weeks on JDK 7 and the latest development version of NetBeans, I have never encountered the bug. Feel free to close it.