| Summary: | Web process crash causes UI process to die with an assertion failure in Connection::exceptionSourceEventHandler | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Mark Rowe (bdash) <mrowe> | ||||
| Component: | WebKit2 | Assignee: | Mark Rowe (bdash) <mrowe> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | andersca, commit-queue, sam | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
Created attachment 235636 [details]
Patch
Comment on attachment 235636 [details] Patch Clearing flags on attachment: 235636 Committed r171715: <http://trac.webkit.org/changeset/171715> All reviewed patches have been landed. Closing bug. |
I've been hitting the following assertion several times a day: // Now send along the message. kern_return_t kr = mach_msg(header, MACH_SEND_MSG, header->msgh_size, 0, MACH_PORT_NULL, MACH_MSG_TIMEOUT_NONE, MACH_PORT_NULL); if (kr != KERN_SUCCESS) { LOG_ERROR("Failed to send message to real exception port. %s (%x)", mach_error_string(kr), kr); ASSERT_NOT_REACHED(); } It typically happens after the web process hits an assertion failure of some sort. Having the UI process die when a web process dies interferes with development.