Closed
Bug 333249
Opened 19 years ago
Closed 18 years ago
synchronous X calls in fast-path GTK2 native theme rendering
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dbaron, Assigned: roc)
References
Details
(Keywords: perf)
There are synchronous XGetGeometry calls even in the fast-path GTK2 native theme rendering, as I described on bug 327878 comment 16. We need to work around the XGetGeometry issue without depending on the GDK API that was just added (see bug 327878 comment 21)
Assignee | ||
Comment 1•19 years ago
|
||
I'm actually a bit surprised by this one, because gdk_pixmap_foreign_new_for_display should only be called once per widget update in most cases, to get a Gdk pixmap for the backbuffer, the first time we draw a native widget into it. After that gdk_pixmap_lookup_for_display should be succeeding until the next time. And one round-trip per widget update shouldn't be eating 25% of our time ... maybe...
I'm looking into it.
Reporter | ||
Comment 2•19 years ago
|
||
Looks like roc attached a patch for this (and that) to bug 333250.
Assignee: nobody → roc
Assignee | ||
Comment 3•19 years ago
|
||
For the record, gdk_pixmap_lookup_for_display was always failing, because pixmap_foreign_new_for_display was creating a proxy and then after we draw one widget with it, we drop our reference to the proxy and it gets deleted right away :-(.
Updated•18 years ago
|
Flags: blocking1.9?
Pretty sure this was fixed by bug 333250.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Updated•18 years ago
|
Flags: in-testsuite-
Updated•18 years ago
|
Flags: blocking1.9?
You need to log in
before you can comment on or make changes to this bug.
Description
•