86467 2012-05-15 04:57:06 -0700 [WK2] crash detected by mistake on Qt-WK2-Linux 2012-05-16 05:50:32 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED INVALID P2 Normal --- 1 kbalazs webkit-unassigned dpranke eric kkristof ossy oldest_to_newest 623904 0 kbalazs 2012-05-15 04:57:06 -0700 This has shown up in connection with https://bugs.webkit.org/show_bug.cgi?id=80691. After I landed the patch that implements plugins with Qt 5 we experiences crashes in some compositing tests. I believe that nrwt detect these as crashes by mistake because of the followings reasons: 1. the crash log produced by nrwt is quite strange: crash log for WebProcess (pid <unknown>): STDOUT: <empty> STDERR: <empty> 2. I could not get any core dump for the tests I tried to debug this via core dumps, because the crashes only occur if you run all the tests, but no dump has generated. Obviously I set up the env for this, i.e. ulimit -c unlimited + export QT_WEBKIT2_DEBUG=1 (the latter makes the Qt WTR to not to install signal handlers). 3. There are no crash with ORWT 624024 1 ossy 2012-05-15 06:55:20 -0700 I managed to reproduce it with ORWT too, so it isn't NRWT bug. You can reproduce it simple if you pass the tests_run0.txt to ORWT --nthly 99999 . (Because ORWT runs tests in different oreder and restart DRT/WTR after 1000 tests if you don't override it with --nthly option) ORWT and NRWT handles WebProcess crashes in the same way, they only parse the output of WTR. If there is any "#CRASHED - WebProcess" line, it reports that WebProcess crashed. So maybe the bug is in WTR. 625328 2 kbalazs 2012-05-16 05:50:32 -0700 The real bug is that sometimes we don't differentiate between web process timeout vs. crash. Indeed, this is not an nrwt issue.