[meta] Blank /Slow devtools after switching to JSProcessActors
Categories
(DevTools :: General, task)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Unassigned)
References
(Depends on 5 open bugs)
Details
(Keywords: meta)
Just a meta to keep track of all issues related to blank devtools on startup, most likely linked to hanging / blocked processes.
We have had many reports in the last months, but the bugs are spread and not linked to each other.
|
Reporter | |
Updated•16 days ago
|
|
|
Reporter | |
Comment 1•16 days ago
|
||
Let's also include reports mentioning slow devtools, ie hanging with a blank state for seconds/minutes before showing anything.
|
|
Reporter | |
Updated•16 days ago
|
|
||
Comment 2•10 days ago
|
||
Is there a way we can make it more obvious what might be happening with logging or something?
|
||
Comment 3•10 days ago
|
||
A discussion is ongoing in bug 1918267 with reason why this happens and I'll attempt to fix these issues there.
|
|
Reporter | |
Comment 4•5 days ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #2)
Is there a way we can make it more obvious what might be happening with logging or something?
:ochameau is adding some logs in his patches for Bug 1918267, should help already to identifies the processes slowing down the DevTools opening. If the issue persists after this patch lands, we should display something directly in the toolbox I think.
Description
•