Bug 24469
| Summary: | Big performance improvement to FontQt.cpp and hence all text drawing and layouting in QtWebKit | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Adam Treat <manyoso> |
| Component: | WebKit Qt | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Other | ||
| OS: | All | ||
Adam Treat
Hi,
Currently the QtWebKit class FontQt.cpp is using a very expensive method to effectively inform Qt's text engine that it should substitute glyphs for particular unicode characters with another unicode character. Right now FontQt.cpp is reconstructing a QString based on a TextRun and then detaching and memcpy'ing whenever it encounters a character that should be treated differently by Qt's text engine according to WebCore::Font::treatAsSpace and WebCore::Font::treatAsZeroWidthSpace.
Profiling shows that this is one of the top ten most expensive methods in all of QtWebKit right now.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Adam Treat
*** This bug has been marked as a duplicate of 24468 ***