| Summary: | [GTK] WebKit web engine crashed | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Johny Why <johnywhy> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | aperez, bugs-noreply, johnywhy, mcatanzaro |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=209900 | ||
|
Description
Johny Why
2020-05-16 11:29:23 PDT
For the critical in “webkit_web_context_register_uri_scheme()“ see bug #209900 — applications should not try to register custom URI scheme handlers for a few schemes that are handled internally by WebKit. Nowadays we return early from that function instead of attempting to register the handler and then crash with a seemingly unrelated assertion deeper inside WebKit. Nevertheless, quick question: unless “G_DEBUG=fatal-warnings“ is set in the environment, that should not be the reason of the crash. Is there any chance you could run the process under GDB to get a backtrace? Alternatively, if your system has “coredumpctl” you may be able to get the backtrace from it. That would help us figuew out what the issue is here, otherwise I am afraid we won't be able to do much. Thanks for your time! No backtrace and therefore no evidence the crash is caused by WebKit. Please, see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for instructions on how to report crashes. I've attached a patch in bug #209900 but there's really no evidence that is related to this issue. |