Closed Bug 1057202 Opened 6 years ago Closed 2 months ago

Codemirror repeatedly slowing down the browser.

Categories

(DevTools :: General, defect)

31 Branch
x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: lb1.3, Unassigned)

Details

(Keywords: perf)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140715214327

Steps to reproduce:

Opened a certain page with the Devtools running


Actual results:

I always got several script-not-responding messages caused by codemirror, including:

chrome://browser/content/devtools/codemirror/codemirror.js:1432
chrome://browser/content/devtools/codemirror/codemirror.js:6416
chrome://browser/content/devtools/codemirror/codemirror.js:480
chrome://browser/content/devtools/codemirror/codemirror.js:3445
chrome://browser/content/devtools/codemirror/codemirror.js:3445




Expected results:

It shouldn't repeatedly have problems like this just opening a page. The lines it's taking a long time on are related to scrolling to a certain position, aligning horizontally, and other things that definitely shouldn't be happening when the page is opened and the Console is open.
Can you provide a test page where you see this happening?
Component: Untriaged → Developer Tools
Flags: needinfo?(lb1.3)
Any simple page, this will do:

<html>

<body>
<div>
Hello 

1. open the page.
2. Ctrl+U, look at it, move source window away
3. F12, look at console.
4. Edit this file, change text.
5. Reload the page, Ctrl+U and notice it shows the OLD source instead of the new text that is actually shown on the page.
</div>

</body></html>
Flags: needinfo?(lb1.3)
Keywords: perf
Product: Firefox → DevTools

There is no specific test case (nor activity) I could follow.

In any case, Code-Mirror slowness is known problem and there are bug reports covering this issue (e.g. bug 1655721, in the Network panel)

Honza

Status: UNCONFIRMED → RESOLVED
Closed: 2 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.