Closed
Bug 1508747
Opened 5 years ago
Closed 4 years ago
UI stops updating completely even though browser is responsive to commands through macOS menubar
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: jya, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
859.10 KB,
image/png
|
Details |
It has happened three times today and as far as I understood it, it has happened to others to. 1st time it occurs during a webrtc call. Suddenly the image froze, however I could still here the other person and that person could see and hear me fine. However, while macOS menu worked fine, I could no longer open a new tab or switch tab. It was totally frozen. I had to quit (no need to force quit, Command-Q worked) 2nd time: I just opened a new tab and entered an URL. While the page was loading and everything froze. Behaviour was as time #1: couldn't select another tab, couldn't open a new tab or close a tab. Command-Q worked fine. 3rd time: I got back after dinner and found the system to be in the same above states. You can quit firefox with keyboard shortcut, access the menu with the mouse, everything else is non-responsive.
Reporter | ||
Comment 1•5 years ago
|
||
so far it has happened on mac only, I have webrender enabled if that matters
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86_64
Comment 2•5 years ago
|
||
I've seen what sounds like this on Windows10 x64 with WebRender enabled, also when opening an appear.in tab for a WebRTC meeting.
Comment 3•5 years ago
|
||
If anyone has a reliable repro for this, could you try enable the WR debug overlay (gfx.webrender.debug.profiler) and report what values you see for the "Texture RGBA8 cached pages" profile counter?
Reporter | ||
Comment 4•5 years ago
|
||
Is webrender what's used to paint the tabs etc? when it's frozen like that, and I attempt to resize the window it will become entirely black. It's happened to me twice again since, each time within a appear.in webrtc call. However, that doesn't mean much because all I've been doing tonith is webrtc call and I've had a case occurring outside a video call.
Comment 5•5 years ago
|
||
In this state, do other shortcuts work, like command-t to open a tab? I'm a bit confused because comment #0 says both that the menu works and that you couldn't open a new tab. A profile would be helpful, or even just knowing whether the main process is hung (using 100% cpu or whatever) according to activity monitor.
Flags: needinfo?(jyavenard)
Reporter | ||
Comment 6•5 years ago
|
||
It's hard to tell because there's no visual confirmation of any kind that anything is happening. So shortcut may well work I just can't tell. Command-Q shortcut worked. :padenot was saying that in this situation (it happened to him last Friday) he could actually using the keyboard go to YouTube, select a song and hear it play. All blind of course as nothing was painted. Next time it happens I'll try again. When I said the menu worked, I mean I could click on the menu on top of the screen, it would open etc, which wouldn't happened if the application was really frozen. Command-T may have opened a tab, I wouldn't be able to tell once the issue occurs.
Flags: needinfo?(jyavenard)
Comment 7•5 years ago
|
||
(In reply to :Gijs (he/him) from comment #5) > In this state, do other shortcuts work, like command-t to open a tab? I'm a > bit confused because comment #0 says both that the menu works and that you > couldn't open a new tab. > > A profile would be helpful, or even just knowing whether the main process is > hung (using 100% cpu or whatever) according to activity monitor. CPU usage was normal, profile does not show anything strange. This is not a performance issue, this is a bug. I had the mini Web Render indicator running (the one that is a strip on the top left), and it was frozen.
Comment 8•5 years ago
|
||
(In reply to Jean-Yves Avenard [:jya] from comment #6) > It's hard to tell because there's no visual confirmation of any kind that > anything is happening. So shortcut may well work I just can't tell. > Command-Q shortcut worked. > > :padenot was saying that in this situation (it happened to him last Friday) > he could actually using the keyboard go to YouTube, select a song and hear > it play. All blind of course as nothing was painted. Next time it happens > I'll try again. > > When I said the menu worked, I mean I could click on the menu on top of the > screen, it would open etc, which wouldn't happened if the application was > really frozen. > Command-T may have opened a tab, I wouldn't be able to tell once the issue > occurs. If you open a new window using the menu, does that appear, and if not, does it appear in the window menu list? :-) Anyway, sounds like a graphics problem so far rather than the frontend JS being wonky or something in that direction.
Component: General → Graphics: WebRender
Product: Firefox → Core
Updated•5 years ago
|
Summary: Regular complete freeze though menu still works → UI stops updating completely even though browser is responsive to commands through macOS menubar
Updated•5 years ago
|
Priority: -- → P2
Comment 9•5 years ago
|
||
(In reply to Paul Adenot (:padenot) from comment #7) > (In reply to :Gijs (he/him) from comment #5) > > In this state, do other shortcuts work, like command-t to open a tab? I'm a > > bit confused because comment #0 says both that the menu works and that you > > couldn't open a new tab. > > > > A profile would be helpful, or even just knowing whether the main process is > > hung (using 100% cpu or whatever) according to activity monitor. > > CPU usage was normal, profile does not show anything strange. This is not a > performance issue, this is a bug. > > I had the mini Web Render indicator running (the one that is a strip on the > top left), and it was frozen. Follow up. I had this again during a 1:1 call, and opening other Firefox windows such as the Library on its own was working fine. Again, the person I was talking with didn't notice anything, everything seem to be working well apart from the display.
Comment 10•5 years ago
|
||
Follow up, I had this again during a 1:1 call, and I blindly dragged the tab that was doing WebRTC (using appear.in) out, to make it a new window, and it started painting again. Additionally, I noticed that on the frozen window, the tabs had no glyphs painted, only the favicons, attaching a screenshot of that.
Comment 11•5 years ago
|
||
The Web Render activity thing on the top left was frozen as well.
Comment 12•5 years ago
|
||
Related to bug 1509161 / bug 1510275 or bug 1510447 comment 5 ?
Updated•5 years ago
|
Blocks: wr-mac, stage-wr-next
Updated•4 years ago
|
Blocks: wr-mac-block
Comment 13•4 years ago
|
||
Curious if either of you have encountered this again?
Flags: needinfo?(padenot)
Flags: needinfo?(jyavenard)
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•