Bug 24469 - Big performance improvement to FontQt.cpp and hence all text drawing and layouting in QtWebKit
Summary: Big performance improvement to FontQt.cpp and hence all text drawing and layo...
Status: RESOLVED DUPLICATE of bug 24468
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Qt (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-09 13:26 PDT by Adam Treat
Modified: 2009-03-09 13:30 PDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Treat 2009-03-09 13:26:13 PDT 
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.
Comment 1 Adam Treat 2009-03-09 13:30:15 PDT 

*** This bug has been marked as a duplicate of 24468 ***