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 090803) VM: OpenJDK Client VM, 14.0-b08, OpenJDK Runtime Environment, 1.6.0_0-b14 OS: Linux, 2.6.28-14-generic, i386 User Comments: dynamite: Opening a new file via the "Go To Type" dialog. Maximum slowness yet reported was 41593 ms, average is 41593
Created attachment 85806 [details] nps snapshot
I don't follow why this was moved from performance to platform. The error is either in the performance tracking tool or in jdk's native calls. reassigning to winsys guys, a likely candidate for "invalid/wontfix" issue.
There seems to be a lot of such slowness reports. They happen on GTK only. So I guess the snapshot tool is giving us consistent results, nothing random. We definitely seek help from our Swing gurus (thus assigned to platform/window system). If there is nothing NetBeans can do, then please help us report this issue to JDK team and mark as a JDK bug. Btw. slightly suspicious is that the problem often happens when painting Tabs.
swing guru says: the bulk of wait time is in native paint methods (nativeFinishPainting) nothing to fix here so it's either a bug in graphics driver or a bug in jdk, note that reported jdk version is 1.6 *update 0*
Created attachment 85966 [details] Showing the part of snapshot that ends in GTKEngine
Is this reproducible? I see it is reported for Open JDK - does it happen also with Sun JDK? Is it multi display setup? Could I send you patched module so that we can see what input values are passed to GTK paint method?
In issue #169817 this happens with Sun JDK.