multiprocess browser console turns chrome unresponsive
Categories
(DevTools :: Console, defect, P2)
Tracking
(Not tracked)
People
(Reporter: thorin, Unassigned)
Details
Attachments
(1 file)
|
1.01 MB,
image/gif
|
Details |
console.gif
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
- Info: Windows7-64bit, FF82-64bit, practically a vanilla profile
- STR. Sometimes it doesn't trigger for a little while, other times I can get it to happen as soon as I open the browser
- open browser
- open multiprocess console (ctrl-shift-J) - I have mine with "show content messages" checked
- maybe visit a site
- see see attached gif
- notes: regression window
- I first noticed this on approx 22nd August which at the time was 81. It is not present in Beta81/Dev81. Every day in Nightly I test things: I always have the multiprocess console open (Ctrl-Shift-J), with "show content messages" option checked. I always update Nightly at least once a day, often twice. I know the time frame is the 22nd, as I was building a new test from scratch that was a bit perf heavy and the console was "hanging things" from day one with this test from the start, and it had never happened before. That test has a timestamp history on github - first created Aug 22nd
|
Reporter | |
Updated•6 years ago
|
|
||
Comment 1•5 years ago
|
||
So yeah, it's probably a performance issue we're seeing here.
That's not the first we get with the Browser console.
I'm wondering if we should avoid loading cached messages, and have some piece of UI to load them if needed. (maybe only for the Browser Console?)
|
|
Reporter | |
Comment 2•5 years ago
|
||
I've just been using the web console, which TBH is a bit quieter :) Just checked the browser console in nightly 84.0a1 (2020-11-09) and chrome was immediately unresponsive. Can you reproduce, or is there anything you would like me to debug?
|
|
||
Comment 3•5 years ago
|
||
(In reply to Simon Mainey from comment #2)
I've just been using the web console, which TBH is a bit quieter :) Just checked the browser console in nightly 84.0a1 (2020-11-09) and chrome was immediately unresponsive. Can you reproduce, or is there anything you would like me to debug?
Yeah, I can definitely reproduce (and we do have other similar bugs about the Browser Console). Thanks!
|
|
Reporter | |
Comment 4•5 years ago
|
||
I can no longer reproduce in Nightly, although my last test was probably months ago. Maybe it's fission? Feel free to close
|
|
||
Comment 5•5 years ago
|
||
Let's duplicate over another browser console bug
Description
•