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.
Build: NetBeans IDE Dev (Build 200909221401) VM: Java HotSpot(TM) 64-Bit Server VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: Linux, 2.6.28-15-generic, amd64 User Comments: GUEST: Saving PHP file GUEST: Saving PHP files GUEST: Saving change to PHP file GUEST: Just saving a single PHP file GUEST: Saving PHP GUEST: Just saving a PHP file... this is terribly slow! GUEST: Saving PHP files GUEST: Saving PHP changes... jasondonmoyer: invoking the saveall action Maximum slowness yet reported was 10823 ms, average is 8006
Created attachment 88552 [details] nps snapshot
This issue already has 9 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157634
all the reports are invalid, time spent in AWT is just a few milliseconds reassigning to performance team
probably some problem in slowness detector or in the server script that collates performance data, not sure i reassigned to the correct component though...
There is no problem, just the older snapshots did not contain the time a thread was waiting. That's why the time of AWT thread is reported small, but in fact it was blocked all the time. You can see the Object.wait call if you expand it. It's pretty clear what it waits for - there's only one other thread doing something. org.netbeans.editor.GlyphGutter is doing something and require document read lock, which is held by long task of mobility saving the document, so it waits for it to finish, blocking AWT event queue. Reassigning to editor for evaluation if this can be avoided. Maybe it's fixed already, there's no newer report than from 20090802 build.
There have been several fixes in this area during last month. Let's wait if a newer report appears, in the meantime, I'll mark this as FIXED.