Browser becomes unresponsive after some time in a WebRTC Zoom.us session. Wayland
Categories
(Core :: Widget: Gtk, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox86 | --- | unaffected |
| firefox87 | --- | ? |
| firefox88 | --- | unaffected |
People
(Reporter: mbagnara, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
71.24 KB,
application/xhtml+xml
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
WAYLAND_DEBUG=1 firefox
Launch a WebRTC Zoom session and enable camera.
Actual results:
Browser becomes unresponsive after some nondeterministic amount of time.
[2606526.649] wl_callback@75.done(60885813)
[2606526.670] -> wl_surface@105.set_buffer_scale(1)
[2606526.685] -> wl_surface@105.frame(new id wl_callback@75)
[2606526.703] -> wl_surface@105.commit()
[2606526.628] wl_callback@109.done(60885813)
[2606526.761] -> wl_surface@43.set_buffer_scale(1)
[2606526.770] -> wl_surface@43.frame(new id wl_callback@109)
[2606526.784] -> wl_surface@43.commit()
[2606537.448] wl_keyboard@69.leave(45558, wl_surface@41)
[2606537.486] wl_keyboard@28.leave(45558, wl_surface@41)
[2606537.514] xdg_toplevel@47.configure(956, 1027, array)
[2606537.536] xdg_surface@46.configure(45559)
[2606537.575] -> xdg_surface@46.ack_configure(45559)
When I kill the process, the following gets appended to the log:
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
|
||
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
|
||
Comment 2•4 years ago
|
||
Please attach info from about:support page.
Please test latest nightly under Wayland, how-to is here:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binaries
Thanks.
|
||
Comment 4•4 years ago
|
||
@mbagnara, can you reproduce this only on Wayland or also on X11? I am facing similar issues using https://whereby.com on X11 (Fedora 33).
(In reply to devurandom from comment #4)
@mbagnara, can you reproduce this only on Wayland or also on X11? I am facing similar issues using https://whereby.com on X11 (Fedora 33).
I do not have a machine with X11 installed that I can test this on and as far as I know it only affects Wayland.
(In reply to Martin Stránský [:stransky] from comment #2)
Please attach info from about:support page.
Please test latest nightly under Wayland, how-to is here:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binariesThanks.
I downloaded the nightly release and have attempted to replicate the above issue but have not been able to. (However other strange issues with context menu focus were introduced)
|
|
||
Comment 6•4 years ago
|
||
(In reply to mbagnara from comment #5)
I downloaded the nightly release and have attempted to replicate the above issue but have not been able to. (However other strange issues with context menu focus were introduced)
Okay, so I expect this one can be closed then, right?
For the 'context menu focus' file a new bug and CC me there. Please try to attach a screencast of the issue. Also attach info if you use experimental fractional scaling, hidpi or multi-monitor setup.
Thanks.
|
|
||
Comment 7•4 years ago
|
||
@mbagnara: I tried under Wayland and also see Firefox become unresponsive after a while of just playing YouTube videos (no WebRTC / video chat). Other symptoms I see is a single thread (a single PID) constantly consuming 1.5-2 CPU cores and the whole process draining several hundred MiB from the system per minute. Since FF is unresponsive, quitting it using Ctrl+Q takes minutes to have an effect. SIGTERM will close the windows almost instantly, but the processes will still run in the background for a minute-or-so until they exit completely. Do you also observe these symptoms?
(In reply to devurandom from comment #7)
@mbagnara: I tried under Wayland and also see Firefox become unresponsive after a while of just playing YouTube videos (no WebRTC / video chat). Other symptoms I see is a single thread (a single PID) constantly consuming 1.5-2 CPU cores and the whole process draining several hundred MiB from the system per minute. Since FF is unresponsive, quitting it using Ctrl+Q takes minutes to have an effect. SIGTERM will close the windows almost instantly, but the processes will still run in the background for a minute-or-so until they exit completely. Do you also observe these symptoms?
I have not experienced the issue above on my current release of Firefox. I will close this issue but you can feel free to open an additional one if specific to you.
Description
•