Bug 88448
| Summary: | "Process failed to become responsive before timing out" is not very helpful | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jessie Berlin <jberlin> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | dpranke, mitz, slewis, thorton, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Jessie Berlin
The current message was added in http://trac.webkit.org/changeset/119018, and, while a step in the right direction, it doesn't provide much information.
If the web process is unresponsive and we don't get a crash log for it, we should sample it instead of just reporting that the the process failed to become responsive.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/11609028>
Stephanie Lewis
This will require changes to how WebKitTestRunner works. Currently we don't find out the process was unresponsive until after the WTR kills it. We might want to go as far as to build the sampling into WTR.