[Webkit-unassigned] [Bug 87717] New: Unresponsive WebProcesses can be mistaken for crashes.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=87717

           Summary: Unresponsive WebProcesses can be mistaken for crashes.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: slewis at apple.com
                CC: mjs at apple.com, dpranke at chromium.org


WebKitTestRunner reports #CRASHED in two places. The first place, webProcessDidCrash, always writes out a crash report (eventually).
The second spot is when we are resetting the WebProcess.  See https://bugs.webkit.org/show_bug.cgi?id=52757

If it becomes unresponsive the WebProcess is killed, which for all intents and purposes looks like a crash.  However, this makes the WebKit2 tests look very flaky, and creates confusion because no crash logs can be found for the unresponsive processes.

The first step is separating the two types of crashes, and giving an error message when the process was just unresponsive, not crashing.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.