Closed Bug 1606848 Opened 4 years ago Closed 4 years ago

[wayland][webrender] unknown object message set_opaque_region

Categories

(Core :: Graphics: WebRender, defect, P2)

x86_64
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1606751
Tracking Status
firefox73 --- fixed
firefox74 --- fixed

People

(Reporter: kubrick, Unassigned)

References

(Blocks 1 open bug)

Details

With the following configuration:

HW_COMPOSITING : blocked by env: Acceleration blocked by platform
OPENGL_COMPOSITING : unavailable by default: Hardware compositing is disabled
GPU_PROCESS : blocked by runtime: Wayland does not work in the GPU process
WEBRENDER : opt-in by default: WebRender is an opt-in feature
WEBRENDER_QUALIFIED : blocked-vendor-unsupported by env: Unsupported vendor
WEBRENDER_COMPOSITOR : disabled by default: Disabled by default
WEBGPU : disabled by default: Disabled by default

I get frequent crashes with today's version (20200103094738), without a backtrace, but the following error in the logs:
Jan 03 17:15:26 xps16 gnome-shell[55605]: WL: unknown object (3857049061), message set_opaque_region(?o)
Jan 03 17:15:26 xps16 gnome-shell[55605]: WL: error in client communication (pid 59496)
Jan 03 17:15:26 xps16 firefox-bin[59496]: Error 22 (Invalid argument) dispatching to Wayland display.
Jan 03 17:15:26 xps16 firefox-nightly.desktop[62347]: Exiting due to channel error.
Jan 03 17:15:26 xps16 firefox-nightly.desktop[62308]: Exiting due to channel error.
Jan 03 17:15:26 xps16 firefox-nightly.desktop[59661]: Exiting due to channel error.
Jan 03 17:15:26 xps16 firefox-nightly.desktop[59744]: Exiting due to channel error.
Jan 03 17:15:26 xps16 firefox-nightly.desktop[59629]: Exiting due to channel error.
Jan 03 17:15:26 xps16 firefox-nightly.desktop[59648]: [GFX1-]: Receive IPC close with reason=AbnormalShutdown
Jan 03 17:15:26 xps16 firefox-nightly.desktop[61385]: Exiting due to channel error.
Jan 03 17:15:26 xps16 firefox-nightly.desktop[59648]: Exiting due to channel error.
Jan 03 17:15:26 xps16 firefox-nightly.desktop[59573]: Exiting due to channel error.
Jan 03 17:15:26 xps16 firefox-nightly.desktop[59573]: ###!!! [Child][MessageChannel] Error: (msgtype=0x5E0004,name=PImageBridge::Msg_Update) Channel error: cannot send/recv
Jan 03 17:15:26 xps16 firefox-nightly.desktop[61907]: Exiting due to channel error.
Jan 03 17:15:26 xps16 systemd[1977]: gnome-launched-firefox-nightly.desktop-59496.scope: Succeeded.

Can you please run it with "WAYLAND_DEBUG=1" env variable set and attach the output here?
Thanks.

Flags: needinfo?(kubrick)
Blocks: wayland
Priority: -- → P2

Is it possible for moz_container_get_wl_surface and moz_container_set_opaque_region to run in parallel on different threads? The former is also called from the VSync code.

Maybe we should avoid setting the opaque region every time moz_container_get_wl_surface is called. Can we get away with setting it once in moz_container_get_wl_surface, when the surface is created (next to wl_surface_set_input_region); and then in moz_container_set_opaque_region, when the surface exists?

Possible dupe is Bug 1606751, it also contains backtraces.

Is it possible for moz_container_get_wl_surface and moz_container_set_opaque_region to run in parallel on different threads? The former is also called from the VSync code.

Yes, that's possible.

Francois, can you please try to disable webrender, i.e. run Firefox with basic compositor?
Set gfx.webrender.force-disabled to true at about:config and restart Firefox.

Thanks.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(kubrick)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.