92862 2012-08-01 04:25:42 -0700 [Qt][WK2] PerformanceTests/DOM/CreateNodes.html crashes intermittently 2014-02-03 03:21:58 -0800 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) All All RESOLVED INVALID Qt, QtTriaged P1 Critical --- 77037 79668 1 ossy webkit-unassigned allan.jensen andersca hausmann jturcotte kadam kbalazs ossy rniwa sam zarvai zoltan oldest_to_newest 684071 0 ossy 2012-08-01 04:25:42 -0700 PerformanceTests/DOM/CreateNodes.html crashes intermittently on the Qt5 WK2 performance bot with the following message: Running DOM/CreateNodes.html (25 of 99) error: DOM/CreateNodes.html Received an invalid message from the web process with message ID 27004d FAILED -------------------------------------------------------------------------- The bug is easily reproducible manually: $ WebKitBuild/Release/bin/WebKitTestRunner --no-timeout PerformanceTests/DOM/CreateNodes.html or $ Tools/Scripts/run-perf-tests -2 --platform qt-5.0-wk2 DOM/CreateNodes.html 687990 1 ossy 2012-08-06 04:19:18 -0700 WK2 guys, have you got any idea what can be this strange error message? 717033 2 ossy 2012-09-11 03:59:47 -0700 ping? 718280 3 allan.jensen 2012-09-12 06:01:51 -0700 It means that either one of the MESSAGE_CHECK assertions in WebProcessProxy failed, or that the arguments could not be decoded. The first is more likely. 719594 4 kbalazs 2012-09-13 09:41:33 -0700 I can take a look. 729416 5 kbalazs 2012-09-27 04:29:02 -0700 Pretty strange bug. It is not the MESSAGE_CHECK macro but an argument coding issue. Not only it is flaky but I couldn't reproduce it in gdb (no matter whether release or debug build) or with a debug build. Maybe valgrind can help here. 730453 6 kbalazs 2012-09-28 03:39:41 -0700 Ok, I missed it, not sure how confused myself, but in fact this is a failing MESSAGE_CHECK in WebPageProxy::didStartProvisionalLoadForFrame. The frame has already been removed, so it looks like a loader bug. This is not fatal as it does not crash in release and probably not very harmful anyway (this is just a theory). I wonder whether it is qt specific at all. 730742 7 kbalazs 2012-09-28 09:39:22 -0700 This seems to be very tricky and I'm not sure I could fix, so feel free to reassign. 731479 8 kbalazs 2012-10-01 01:43:00 -0700 I could not reproduce it on Mac (Mac port). 732467 9 allan.jensen 2012-10-02 03:20:03 -0700 I can not reproduce it at all locally (Qt5 Linux). 732501 10 ossy 2012-10-02 04:03:39 -0700 (In reply to comment #9) > I can not reproduce it at all locally (Qt5 Linux). But the bug is still valid ... It is reproducible, but not so easy ... As the title of the bug say, it crashes intermittently, not always. So you have to run it many times to catch one crash. Check the bot history: http://build.webkit.org/builders/Qt%20Linux%2064-bit%20Release%20%28WebKit2%20Perf%29?numbuilds=200 There are many fails because of this bug: - http://build.webkit.org/builders/Qt%20Linux%2064-bit%20Release%20%28WebKit2%20Perf%29/builds/4390 - http://build.webkit.org/builders/Qt%20Linux%2064-bit%20Release%20%28WebKit2%20Perf%29/builds/4382 - http://build.webkit.org/builders/Qt%20Linux%2064-bit%20Release%20%28WebKit2%20Perf%29/builds/4377 - http://build.webkit.org/builders/Qt%20Linux%2064-bit%20Release%20%28WebKit2%20Perf%29/builds/4374 - http://build.webkit.org/builders/Qt%20Linux%2064-bit%20Release%20%28WebKit2%20Perf%29/builds/4367 - http://build.webkit.org/builders/Qt%20Linux%2064-bit%20Release%20%28WebKit2%20Perf%29/builds/4352 - http://build.webkit.org/builders/Qt%20Linux%2064-bit%20Release%20%28WebKit2%20Perf%29/builds/4351 - http://build.webkit.org/builders/Qt%20Linux%2064-bit%20Release%20%28WebKit2%20Perf%29/builds/4326 ... 754015 11 ossy 2012-10-30 00:01:21 -0700 The bug is still valid, it still crashes and perf test bot is red almost always because of this bug. 758428 12 ossy 2012-11-05 04:52:21 -0800 Fortunately WTR dumps the name of the message now: Running DOM/CreateNodes.html (31 of 106) error: DOM/CreateNodes.html Received an invalid message "WebPageProxy.DidStartProvisionalLoadForFrame" from the web process. FAILED Finished: 1.305343 s ------------------------------------------------------------------------------ Running DOM/CreateNodes.html (31 of 106) error: DOM/CreateNodes.html Received an invalid message "WebPageProxy.DidInitiateLoadForResource" from the web process. FAILED Finished: 11.734229 s ------------------------------------------------------------------------------ Running DOM/CreateNodes.html (31 of 106) error: DOM/CreateNodes.html Received an invalid message "WebPageProxy.DidSendRequestForResource" from the web process. FAILED Finished: 25.302365 s ------------------------------------------------------------------------------ Running DOM/CreateNodes.html (31 of 106) error: DOM/CreateNodes.html Received an invalid message "WebPageProxy.DidStartProvisionalLoadForFrame" from the web process. FAILED Finished: 5.300999 s ... 838208 13 zarvai 2013-02-21 01:20:49 -0800 After switching Qt Linux 64-bit Release (WebKit2 Perf) bot to Ubuntu 12.04 the PerformanceTests/DOM/CreateNodes.html fails most of the time. 838223 14 kbalazs 2013-02-21 01:51:32 -0800 (In reply to comment #13) > After switching Qt Linux 64-bit Release (WebKit2 Perf) bot to Ubuntu 12.04 the PerformanceTests/DOM/CreateNodes.html fails most of the time. I can imagine that it is related to bug 107633. Could you try running the test with Rafael's WIP fix from there? 838286 15 ossy 2013-02-21 03:22:19 -0800 As I said before, unfortunately we can't reproduce this bug on small example. If we run only this test, it always passes. But on the bot, when it runs all tests, it fails almost always. (Previously it failed only all 5th-10th run) 842747 16 ossy 2013-02-26 23:49:18 -0800 *** Bug 110945 has been marked as a duplicate of this bug. *** 975525 17 jturcotte 2014-02-03 03:21:58 -0800 === 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.