browser permanently hangs when logging tons of stuff

NEW
Unassigned

Status

DevTools
Console
P2
normal
4 years ago
a month ago

People

(Reporter: fitzgen, Unassigned)

Tracking

(Blocks: 2 bugs, {perf, regression})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [console-papercuts][polish-backlog])

Attachments

(3 attachments)

STR:

1. Load http://fitzgen.github.io/ocean-noise/
2. Open a scratchpad
3. Paste attachment into the scratchpad
4. Run the scratchpad
5. Click the big "play" button

ER:

Stuff logs in the console. Failing that, when there are too many messages, some are displayed and the browser is still responsive. Seems like at minimum we could just put some loop inside a DevToolsUtils.yieldingEach[0] or queue up messages to be rendered so that the browser is still responsive.

[0]: http://dxr.mozilla.org/mozilla-central/source/toolkit/devtools/DevToolsUtils.js#171

AR:

Permanent beach ball. Need to force-quit firefox.
Note that if you modify the scrachpad so that `strace.logging = false;` before the `strace(window);` call, there are no issues, so it is definitely a problem with handling that many log messages.
Thanks for the bug report. This might be caused by recent changes/perf regressions. Needs investigation.
Keywords: perf
Priority: -- → P2
Keywords: regression
Created attachment 8465498 [details]
profile-scratchpad.json.zip

profile data from running this in the browser toolbox' profiler.
Created attachment 8465499 [details]
Screen Shot 2014-07-31 at 11.38.01.png

Screenshot of the profiler showing 35% of the time being spent in utils.js cloneObject method.

An additional 11% is being spent in the webconsole.js pruneOutput function.
s/pruneOutput/flushMessageQueue/
Whiteboard: [console-papercuts]
Whiteboard: [console-papercuts] → [console-papercuts][devedition-40]
Whiteboard: [console-papercuts][devedition-40] → [console-papercuts][polish-backlog]
Update: e10s helps a lot here. Instead of the browser beachballing in an unrecoverable way, instead you get the notificationbox popup and can kill the web content process and get the browser back.

Updated

a month ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.