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.
Summary: | 41s in GTK paint of Tabs | ||
---|---|---|---|
Product: | platform | Reporter: | dynamite <dynamite> |
Component: | Window System | Assignee: | issues@platform <issues> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | jtulach, mslama |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=154955 | ||
Issue Type: | DEFECT | Exception Reporter: | 154955 |
Attachments: |
nps snapshot
Showing the part of snapshot that ends in GTKEngine |
Description
dynamite
2009-08-05 08:30:24 UTC
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. |