Fails on Qt WK1 and Qt WK2 --- /ramdisk/qt-linux-32-release-webkit2/build/layout-test-results/http/tests/uri/curly-braces-escaping-expected.txt +++ /ramdisk/qt-linux-32-release-webkit2/build/layout-test-results/http/tests/uri/curly-braces-escaping-actual.txt @@ -3,7 +3,7 @@ On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". -PASS req.responseText is '/uri/resources/echo-uri.php?q={}' +FAIL req.responseText should be /uri/resources/echo-uri.php?q={}. Was /uri/resources/echo-uri.php?q=%7B%7D. PASS successfullyParsed is true TEST COMPLETE http://build.webkit.sed.hu/results/x86-32%20Linux%20Qt%20Release%20WebKit2/r150963%20%2835884%29/results.html
I'm curious whether you get a freeze on <http://www.washingtonpost.com/wp-srv/special/sports/grade-robert-griffin-iii> then.
(In reply to comment #1) > I'm curious whether you get a freeze on <http://www.washingtonpost.com/wp-srv/special/sports/grade-robert-griffin-iii> then. I tried r150852 and the current r150976's MiniBrowser and QtTestBrowser. QtWebProcess and QtTestBrowser went crazy and ate all of my ram. So it occures with WK1 and WK2, too. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 24071 azbest 30 10 14.1g 6.6g 15m D 32 84.7 0:52.29 QtWebProcess 24088 azbest 30 10 2101m 16m 6800 S 1 0.2 0:01.72 QtWebPluginProc If it is not hangs right after start, then scrolling will and some clicking will finish it.
Yes, same symptom. I suggest that you track this by its real life symptom, not just as a regression test failure.
=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.