Context Navigation

Changes between Version 4 and Version 5 of QtWebKitPerformanceToolBackLog:

-              v4
+              v5
 ||loading_standalone was created to reproduce a loading issue with Wikipedia content. Currently it is not able to reproduce the exact same set of problems. The test should be changed to start new downloads from within didReceiveResponse... like in the real case.||||
 ||tst_painting is currently using ''QApplication::syncX'' in the performance run to make sure that everything has been synced. The problem with this paint benchmark is that on accelerated hardware it is not clear when the image has been painted. The ''QApplication::syncX'' will make the test a bit artificial in one way.||||
-||memusage is not working on glibc/i686... this is making us blind on memory usage...||||
 ||Benchmarks should generate more stable timing results.||||
+||~~memusage is not working on glibc/ix86...~~ This is fixed in latest glibc git, more patches to come||[http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=22bc5239e1c7d97b0642af6c135af994586f8e82 memusage.so fix] [http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=67854c131c2ba8c013debf466b20cb13fffa120b memusagestat fixes]||
 ||~~Minor patches to memprof to fix generation of images.~~||[http://gitorious.org/qtwebkit/performance/commit/ba418c4384f98010192e18c69b2b7c20e3c1629a ba418]||
 ||~~Fixed http server to nog hog CPU in case of cancelled requests~~||[http://gitorious.org/qtwebkit/performance/commit/4bc79d68bb20c39b3cb9a3cbf7440fc145999928 4bc79]||