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.

Bug 169859 - 41s in GTK paint of Tabs
Summary: 41s in GTK paint of Tabs
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@platform
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-05 08:30 UTC by dynamite
Modified: 2009-08-20 12:18 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 154955


Attachments
nps snapshot (27.70 KB, bin/nps)
2009-08-05 08:30 UTC, dynamite
Details
Showing the part of snapshot that ends in GTKEngine (64.12 KB, image/png)
2009-08-07 14:17 UTC, Jaroslav Tulach
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dynamite 2009-08-05 08:30:24 UTC
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
Comment 1 dynamite 2009-08-05 08:30:30 UTC
Created attachment 85806 [details]
nps snapshot
Comment 2 Milos Kleint 2009-08-05 10:17:34 UTC
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.
Comment 3 Jaroslav Tulach 2009-08-05 10:24:32 UTC
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.
Comment 4 Stanislav Aubrecht 2009-08-05 10:34:15 UTC
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*
Comment 5 Jaroslav Tulach 2009-08-07 14:17:02 UTC
Created attachment 85966 [details]
Showing the part of snapshot that ends in GTKEngine
Comment 6 mslama 2009-08-20 12:12:56 UTC
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?
Comment 7 mslama 2009-08-20 12:18:24 UTC
In issue #169817 this happens with Sun JDK.