| Summary: | [GTK] UI process crash in webkitWebViewBaseEnterAcceleratedCompositingMode | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> | ||||
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | bugs-noreply, mcatanzaro | ||||
| Priority: | P2 | ||||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Attachments: |
|
||||||
|
Description
Michael Catanzaro
2022-12-06 08:57:10 PST
Created attachment 463909 [details]
Full backtrace
Hit this again today. Tried printing some more stuff:
(gdb) print webkitWebViewBase
$1 = <optimized out>
(gdb) print webkitWebViewBase->priv
value has been optimized out
(gdb) print webkitWebViewBase->priv->acceleratedBackingStore
value has been optimized out
(gdb) print layerTreeContext
$2 = (const WebKit::LayerTreeContext &) @0x7ffd2659c130: {contextID = 1261}
It's frustrating that I can't see what's going on with webkitWebViewBase. I wonder if it has already been disposed.
I guess this could happen if WebKitWebViewBase is disposed but not yet finalized when the IPC message arrives? I doubt that's really happening here, but... who knows, maybe? Could try clearing priv->pageClient in webkitWebViewBaseDispose. |