Backlog of Qt and QtWebKit problems

Qt problems

The QtBackLog was migrated to the JIRA. You can use this ​query.

QtWebKit problems

Bug	Description	Commit	Date
Consider creating a SharedBuffer that works on tiles/segments
​#31849	Loading of ​http://en.wikipedia.org/wiki/Maxwell_equations is triggering bad "scheduling". The loading_standalone test has been extracted but is not able to highlight the problem. This is a Qt and QtWebKit issue, it must be understood first. The first issue is that QtWebKit will only schedule four requests per host while Qt networking has a higher limit.	​r5144 - reduce latency
TCmalloc needs to be tested. Does it make anything faster/slower? How to test memory fragmentation.
The fuzz testing will make QtWebKit go in infinite loops and stop working. This situation needs to be analyzed as this can be a serve reliabality problem.
​#30211	Research a better QImage -> QPixmap migration strategy. Currently we convert every QImage to a QPixmap and this is bad for times where we need to draw a scaled version of the image or will only draw this image once.
​#30293	Loading speed regressed due image changes?
​#30301	Loading bug/API bug on loading amazon in QtEmbedded Linux. Loading does not complete.
​#29279	Decode images to RGB16 or smaller (instead of RGB32) to conserve memory. The patch introduces new API to Qt.
Go through the Palm changes and consider adopting them. Currently candidates are: Use stack/class memory in CSSParser, use JDCT_Fast for Jpeg decoding (to be achieved with QImageReader to set quality to 49), changes to Cached* to throw away encoded data more early. Palm avoids floating point operation on premultiplied alpha in setRGBA.
​#30740	Using QImageReader::setQuality(49) will use JDCT_IFAST and promises to give a 5% speedup on image_cycling.
​#30210	Create Embedded profile that will tune for embedded usage. This can mean to save memory in favor of speed, add a speed gain by avoiding certain operations, trading image quality for speed
​#29443	Using WebCore's FontCache decreases memory usage. Change done by Benjamin Poulain
​#31009	Implement throwing away frames from big GIF animations. This requires QImageReader allow to efficently jumping to a given image.
Change CursorQt.cpp to not create QPixmap's right away but only on first load. This will be a minor memory improvement. Using DEFINE_LOCAL_STATIC had a negative impact on memory usage.
​#27538	Image decoder changes needs to be measured. Do they make anything faster/slower? Do they consume more or less memory?	​49179 ​49180 ​49181 ​49182 ​49183 ​49185 ​49186 ​49559	6.10.2009-14.10.2009
​#30769	Export fastMalloc, fastCalloc, fastRealloc and fastFree on GCC/Unix	​50204 ​50205	28.10.2009
Misc Changes
​#31203	Qt Plugins become visible even if they should not	​#51410 (automate test case) ​#51409 (fix)	25.11.2009
​#30209	Document a feature of the m_liveDecderResources list	​50213	28.10.2009
​#27347	Fix assertion in SVGRenderBase::mapLocalToContainer	​50207	28.10.2009
​#30820	Custom Cursor doesn't use hotspot	​50206	28.10.2009

Legend

Completion

An item that is strokethrough means it was completed and no further work needs to be done. An item is considered completed when the related bug report is closed, all patches has been landed to WebKit or Qt and links to the commits and the date of the landing is entered to the table.

Branch

For Qt patches the branch is pointing to a branch that needs to be merged into the Qt source tree. The branch has a specific topic and all patches of this branch are meant to be merged there. The patches are backed with performance tests and the Qt regression test suite was fully or partially executed on them.

Landed in

Landed in should point to the git commit/commits when the branch has been merged into the Qt main repository. After this has happened and no regressions are found the item is considered completed.

Commit

Commit refers to a commit into the WebKit svn repository. Only after changes have landed in the repository the change is considered to be completed.