Closed Bug 739168 Opened 14 years ago Closed 13 years ago

hang in JS parser

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: glazou, Unassigned)

References

()

Details

(Keywords: regression)

The attached URL freezes Nightly Gecko/20120325 Firefox/14.0a1 (Built from http://hg.mozilla.org/mozilla-central/rev/20a01901480f) on both Mac OS X (tested by myself) and Win64 (tested by Neil Rashbrook). Neil said on IRC it is hanging in the JS parser, hence the bug component and bug summary chosen. That's a regression, it works for me on a 20120324 Mac OS X build built from mozilla-central rev df1f94b2bdee.
It turns out that I had strict JS warnings enabled, and my console had filled with a huge number of copies of the following warning: JavaScript warning: http://www.google.com/uds/api/elements/1.0/79d660335e8f0082088b4c7944ed5eb3/inputtools.js, line 1: octal literals and octal escape sequences are deprecated
The warning in comment 1 is new, and expected.... The fact that strict warning can cause lots of slowness is known and has existing bugs covering it.
Not tracking because it's a long-known bug.
That doesn't really help. That strict warnings can cause slowness may be a long-known bug, but if a new warning is triggered a lot (and we can't get rid of the overhead) it may mean we have to disable the warning.
dcamp, do you remember this stuff about lots of warnings going the console causing slowdowns? bz refers to it above, and ISTR something like that, but I can't actually find the existing bugs.
I don't know of any. Mihai or Rob, do you guys remember any bugs about console errors causing slowdowns?
Bug 634444 may be relevant if there are long lines involved.
we have this: https://bugzilla.mozilla.org/show_bug.cgi?id=722685 though not really related to Console Logging itself being slow.
I don't think I've seen bug 722685 before but it looks related. I think bug 634444 is the one I remember from a while back.
Bug 634444 looks pretty similar to this bug.
So this only affects people having a console open?
Removing my tracking request under the assumption that this doesn't affect ordinary users...
Bug 634444 was fixed a long time ago. I'm assuming it fixes this problem. Please reopen if not.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.