Closed
Bug 1288899
Opened 9 years ago
Closed 2 years ago
Enabling javascript.options.strict causes a short freeze while loading reCAPTCHA
Categories
(Core :: JavaScript Engine, defect, P3)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: peter, Unassigned)
Details
(Keywords: triage-deferred)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160630070928
Steps to reproduce:
1. Create a new browser profile (optional)
2. Go to about:config, enable javascript.options.strict
3. Open https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Additional details:
Reproduced with Firefox 47.0.1, but this problem has existed for a while. Recently it was very noticable since (accidentally) opening the listinfo page with a reCAPTCHA always causes this freeze.
Environment: i7-6700HQ (but it also occurred on an older i5-560M) on Arch Linux x86_64.
Actual results:
The browser freezes for 3-4 seconds, scrolling only updates after seconds.
Expected results:
Page should load instantly with no stuttering or freezing the browser. (Compare it javascript.options.strict=false).
Comment 1•9 years ago
|
||
Web console gets flooded by "ReferenceError: deprecated caller usage" warnings, more than 95000 times...
> ReferenceError: deprecated caller usage [Learn More]
> TWEJNgvmTd8UZqkJU0wMyujNp6bYaObsPYUi0tZwwqE.js%20line%201%20%3E%20eval:1:5225
Also, the warning happens at different column almost everytime, so those reports are not merged to previous one.
I think our warning reporting mechanism is not designed to be able to handle so much warnings reported at once.
Maybe, we can avoid such case by reporting deprecated usage warning only once per compartment, or limiting the maximum number?
Status: UNCONFIRMED → NEW
Ever confirmed: true
The warning flood appeared after pushlog https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0b9dd32d1e16&tochange=64c4ec2df3d4
I guess it's due to Bug 969478.
Updated•7 years ago
|
Keywords: triage-deferred
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•