Devtools slow and occasionally unresponsive on some sites

jdescottes · January 8, 2018, 8:56am

| Any news on this front […] Using FF 57.0.3

Stepping (F10) performance has been improved on 59 already. “Opening the debugger” can be slow for various reasons, we are still working on improvements related to sourcemaps. If you have a link with steps to reproduce your issue, the best is to open a ticket on https://github.com/devtools-html/debugger.html/issues

Always worth trying Nightly, as we have been landing several performance improvements to the debugger in Firefox 59.

| I have another issue where a bunch of breakpoints keep coming back
| no matter how many times I remove them.

I thought most “breakpoints” issues were fixed before 57 . As a workaround you should be able to go to about:config and look for “devtools.debugger.pending-breakpoints”. Could you copy the value and report it here? After that you can right click and “Reset” the value. Hopefully it should remove those persistent breakpoints.

adin · January 8, 2018, 9:21am

Hi, I’ll check out the Nightly .
I’d rather not have the contents of “devtools.debugger.pending-breakpoints” on a website. Can I send it to you privately?

Guirec_Corbel · January 8, 2018, 1:29pm

I still have the issue with Firefox 59. A single tab opened with the debugger take 5Go of RAM.

Guirec_Corbel · January 21, 2018, 7:14pm

I just created this bug report : https://bugzilla.mozilla.org/show_bug.cgi?id=1432051

Guirec_Corbel · February 18, 2018, 4:40pm

Hi,

Jason Laster did a huge job to improve perf and it’s a lot better with Firefox 60a1, the current nightly build.

You can visit this repo if you want more about the debugger.

robertleeplummerjr · October 31, 2018, 2:01pm

I’m able to reproduce, and working on a project that is open source, called GPU.js. I’d like to help solve this as it is the one hangup in firefox that has me switching back (temporarily) to other browsers.

To reproduce:

Clone this - git@github.com:gpujs/gpu.js.git
Run npm i or yarn to install node packages (mostly just QUnit)
Start webserver from root
Visit (replace “localhost:8000” with your path) http://localhost:8000/test/all/html
Filter on any of the tests, example: “#195” put a breakpoint in gpu.js around here - https://github.com/gpujs/gpu.js/blob/43bb07e879dc6f6085c45a825b6823e8a78e8ac8/bin/gpu.js#L3207 (return statement of astMemberExpression of the WebGLFunctionNode class)
Refresh the page, and see how breakpoint changes locations erratically, and causes the debugging environment to freeze up and become unresponsive.

I can reproduce this 10 of 10 times on an i7 MacBook Pro. This is likely over-exasperating Firefox, because this function is somewhat highly recursive, but it will quickly exemplify the problem in a compounded way. Chrome, 10 of 10 times, has no issue whatsoever loading the debugger.

I hope this can help!