[Webkit-unassigned] [Bug 41682] Certain page elements cause XGetImage and software fallback rendering
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jul 19 08:11:55 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=41682
Ariya Hidayat <ariya.hidayat at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ariya.hidayat at gmail.com
--- Comment #10 from Ariya Hidayat <ariya.hidayat at gmail.com> 2010-07-19 08:11:55 PST ---
First of all, can you at least kindly verify that my patch solves your excessive XGetImage problem? Note that Qt X11 is a complex and delicate paint engine (and very few people know the code well), my recommendation is always to put any workarounds outside Qt X11 because otherwise you may risk breaking too much.
As for XPutImage, you need to give more information. Is my reduced test case triggering that problem, too? Or do I need to create another reduced test from the atlas map? Do you know which functions in Qt painting is the source of the XPutImage problem? Do you have a code path?
Note that it was not too difficult for me to analyze and solve the XGetImage problem, because all I did were sprinkling breakpoints around XGetImage in Qt X11, running the complex test case, checking the stack trace, reducing the test case, and then looking for the workaround. Would it be too much to ask if you could do the same for the said XPutImage problem?
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list