Bug 193117
| Summary: | [WPE][GTK] WEBKIT_WEB_PROCESS_CRASHED should not trigger on Ctrl+C | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | bugs-noreply |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=221489 | ||
Michael Catanzaro
$ epiphany
^C
** (epiphany:2): WARNING **: 13:46:18.727: Web process crashed
** (epiphany:2): WARNING **: 13:46:18.727: Web process crashed
** (epiphany:2): WARNING **: 13:46:18.727: Web process crashed
** (epiphany:2): WARNING **: 13:46:18.727: Web process crashed
** (epiphany:2): WARNING **: 13:46:18.727: Web process crashed
SIGINT causes one "web process crashed" warning to print per open tab. It's because web-process-terminated is emitted with WEBKIT_WEB_PROCESS_CRASHED whenever WebKit's IPC socket is closed (SIGHUP) without checking the exit status of the child process. We should really add a new WebKitWebProcessTerminationReason to account for stuff like this. SIGINT is not a crash, nor is SIGTERM or SIGKILL. Crashes are for SIGSEGV, SIGABRT, SIGILL, SIGBUS, etc.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |