968976 - Long lines in the web console kills browser responsiveness and uses lots of cpu

Status: RESOLVED WORKSFORME

(DevTools :: Console, defect, P2)

Description

[Olli Pettay [:smaug][[e-mail]]]

When webconsole needs to deal with long lines, it seems to use tons of cpu time
when doing reflow. One issue is that is uses timer, not animation frame callback to do its
stuff, and other issue is probably that is just does too much.

Could we perhaps cut overlong lines?

(I don't have a STR)

Comment 1

[Mihai Sucan [:msucan]]

Probably related to bug 951753.

Comment 2

[nemo]

http://www.pbs.org/newshour/making-sense/is-your-money-safe-at-the-bank-an-economist-says-no-and-withdraws-his/

Password fields present on an insecure (http://) iframe. This is a security risk that allows user login credentials 
to be stolen.[Learn More]
message {target: Window → is-your-money-safe-at-the-bank-an-economist-says-no-and-withdraws-his, data: 
"rdy=1&geo=&bti=&bts=1&vts=0&ssc=&nt=cs%3B328%2Cce%3B328%2Cdc%3B2131%2Cdclee%3B2131%2Cdcles%3B2131%2Cdi%3B1731%2Cdl%3B1449%2Cdle%3B328%2Cdls%3B328%2Cfs%3B328%2Clee%3Bu%2Cles%3B2131%2Cns%3B0%2Crs%3B775%2Crspe%3B1175%2Crsps%3B1174%2Cscs%3Bu&uid=x&ups=", origin: 
"https://ct1.addthis.com", lastEventId: "", source: Object → sh148.html, isTrusted: false, eventPhase: 0, bubbles: 
false, cancelable: true, defaultPrevented: false, timeStamp: 1391695045757615} jquery.cove-videoplayer.js:199

7,681 characters.

I've run into this problem, although not as severe, with shorter lines in the console though.
BTW, another case of "must show all the things" that I encountered w/ FF, still unfixed.
http://m8y.org/tmp/zipbomb/test.html
http://m8y.org/tmp/zipbomb/  (dir contents)

Comment 3

[Soledad Penades [:sole] [:spenades]]

I can't reproduce this (yeah... three years later). Sorry!

Comment 4

[nemo]

how did you go about reproducing. want to test locally.  can you give me a link with similarly long console lines to that 8k one from the past?

Comment 5

[Soledad Penades [:sole] [:spenades]]

I opened the link you provided, with the console open. They have probably changed the code. If you build a test case that reproduces the error I'd be happy to draw attention to it :)

Comment 6

[Nicolas Chevobbe [:nchevobbe]]

In order to reproduce in the new console, we need Bug 1310630, which I'm working on.

Comment 7

[nemo]

re comment #5
ok... just seems wrong to mark WORKSFORME  if a demo site from 3 years ago 404'd or removed some broken code that was being used as a testcase... doesn't change the bug...  WORKSFORME would be id you generated an 8k line in the console(s) and it didn't burn CPU 

Comment 8

[Mike Hoye [:mhoye]]

When it works for me given the provided test case, "WORSKFORME" is the right call. 

If you can provide an example that re-exhibits the behavior in question we can reopen this, but without it this is not an actionable bug.