Bug 261733

Summary:	[GTK] Playing videos on odysee.com breaks network process
Product:	WebKit	Reporter:	Michael Catanzaro <mcatanzaro>
Component:	WebKitGTK	Assignee:	Nobody <webkit-unassigned>
Status:	NEW ---
Severity:	Normal	CC:	bugs-noreply, mcatanzaro, nekohayo, pgriffis
Priority:	P2
Version:	WebKit Nightly Build
Hardware:	PC
OS:	Linux

Description Michael Catanzaro 2023-09-19 05:52:27 PDT

Visit https://odysee.com/@GraysonPeddie:6/gnome-mag-obs:5 and try to play the video. Networking will break in all browser tabs.

My always-open Element tab says:

"""
Database unexpectedly closed

This may be caused by having the app open in multiple tabs or due to clearing browser data.
"""

In practice, this error message usually corresponds to a WebKitNetworkProcess crash; however, in this case, the network process does not crash.

Trying to load other websites in new tabs results in the "WebKit encountered an internal error" error page that also generally corresponds to a network process crash.

The odysee page itself will display one of two error messages. It might present the error "A network error caused the media download to fail part-way" on top of the video itself, or it might display a banner at the bottom of the page warning that you are offline.

Suffice to say, something is wrong in the network process. It's a real shame that it's not actually crashing, because that would make it much easier to figure out what is wrong.

Comment 1 Patrick Griffis 2023-11-13 12:03:29 PST

It crashes here but I don't have a great callstack:

__cxa_throw (@__cxa_throw:3)
___lldb_unnamed_symbol355 (@___lldb_unnamed_symbol355:13)
px_proxy_factory_get_proxies (@px_proxy_factory_get_proxies:1622)
___lldb_unnamed_symbol105 (@___lldb_unnamed_symbol105:37)
___lldb_unnamed_symbol5310 (@___lldb_unnamed_symbol5310:32)
___lldb_unnamed_symbol2644 (@___lldb_unnamed_symbol2644:102)
___lldb_unnamed_symbol2629 (@___lldb_unnamed_symbol2629:25)
start_thread (@start_thread:163)
__clone3 (@__clone3:20)

Comment 2 Michael Catanzaro 2023-11-13 13:09:36 PST

Well yours is crashing in libproxy so I'm pretty sure your bug is different from mine. I'm curious to know what your system proxy config looks like. For myself and most users, it's empty.

My WebKit is definitely not crashing. This has recently become a frequent problem affecting many websites; in fact, I saw this bug again earlier today, but don't remember on which website. It just happens randomly anywhere. I think we decided that nghttp2 can return "internal error" to libsoup; maybe libsoup is passing that along to WebKit somehow?

It's coming from here:

WebCore/platform/network/ResourceErrorBase.cpp:    return ResourceError("WebKitErrorDomain"_s, 300, url, WEB_UI_STRING("WebKit encountered an internal error", "WebKitErrorInternal description"));