Closed
Bug 653890
Opened 13 years ago
Closed 12 years ago
Performance lag on the certain site, The browser stalls for approximately 5 seconds after page is loading.(if set javascript.options.strict to true)
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 634444
People
(Reporter: alice0775, Unassigned)
References
()
Details
(Keywords: regression, Whiteboard: [MemShrink])
Build Identifier: http://hg.mozilla.org/releases/mozilla-2.0/rev/9b8188993c1a Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.2pre) Gecko/20110425 Firefox/4.0.2pre ID:20110425030533 Performance lag on the certain site. The browser stalls for approximately 5 seconds after page is loading. Steps to Reproduce: 1. Start Firefox with new profile(no-addon) 2. Open URL ( http://googlereader.blogspot.com/2010/01/follow-changes-to-any-website.html ) 3. Scroll up/down by mouse wheel. optionally 4. Reload (F5) 5. Scroll up/down by mouse wheel. Actual Results: The browser stalls for approximately 5 seconds after page is loading. I cannot scroll page. Expected Results: The browser should not stall. I can scroll page immediately. Regression window(cached m-c hourly): Work: http://hg.mozilla.org/mozilla-central/rev/4c5f51f5e9a0 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101209 Firefox/4.0b8pre ID:20101209102944 Fails: http://hg.mozilla.org/mozilla-central/rev/58dcad7165be Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101209 Firefox/4.0b8pre ID:20101209104124 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4c5f51f5e9a0&tochange=58dcad7165be Regression window(cached TM hourly): Work: http://hg.mozilla.org/tracemonkey/rev/dadc1d60b6f3 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101207 Firefox/4.0b8pre ID:20101207110318 Fails: http://hg.mozilla.org/tracemonkey/rev/2b9d805d77a1 Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:2.0b8pre) Gecko/20101208 Firefox/4.0b8pre ID:20101208092152 Pushlog: http://hg.mozilla.org/tracemonkey/pushloghtml?fromchange=dadc1d60b6f3&tochange=2b9d805d77a1
Reporter | ||
Comment 1•13 years ago
|
||
It also happens on http://hg.mozilla.org/mozilla-central/rev/88d3c5bde0ba Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0a1) Gecko/20110429 Firefox/6.0a1 ID:20110429030623 , http://hg.mozilla.org/mozilla-central/rev/88d3c5bde0ba Mozilla/5.0 (X11; Linux i686; rv:6.0a1) Gecko/20110429 Firefox/6.0a1 ID:20110429030623
Reporter | ||
Updated•13 years ago
|
Comment 2•13 years ago
|
||
Hmm. I can't seem to reproduce.... do you have firebug active during the pageload or the error console or web console open (hence the dep on bug 634444)?
Reporter | ||
Comment 3•13 years ago
|
||
(In reply to comment #2) > Hmm. I can't seem to reproduce.... do you have firebug active during the > pageload or the error console or web console open (hence the dep on bug > 634444)? No, I tried with new profile(no-addon). but you should set javascript.options.strict to true. And I notice 100% core usage for about 5 sec in TaksManager.
Summary: Performance lag on the certain site, The browser stalls for approximately 5 seconds after page is loading. → Performance lag on the certain site, The browser stalls for approximately 5 seconds after page is loading.(if set javascript.options.strict to true)
Comment 4•13 years ago
|
||
Ah, with options.strict that explains the dependency. Alright. ;)
Comment 5•13 years ago
|
||
With strict on, the site seems to generate a huge number of errors like this: [06:44:13.735] octal literals and octal escape sequences are deprecated @ http://www.blogger.com/static/v1/widgets/4286431867-widgets.js:81 This doesn't seem like a bug in Fx to me.
Comment 6•13 years ago
|
||
The Fx bug is that reporting those errors is so slow. That's what bug 634444 is about.
Comment 7•13 years ago
|
||
Who actually turns strict on? It doesn't seem like a very useful feature to me. Maybe if you're working on your own site and you want it to pass, but for general browsing it seems pointless. (Having said that, I still want to fix bug 634444.)
Comment 8•13 years ago
|
||
> Who actually turns strict on?
People doing front-end development (where it can help catch issues) or web QA (likewise).
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Whiteboard: [MemShrink]
You need to log in
before you can comment on or make changes to this bug.
Description
•