Closed
Bug 1142077
Opened 9 years ago
Closed 9 years ago
Unresponsive script on Whatsapp web
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: swstar, Unassigned)
References
()
Details
(Keywords: regression, reproducible)
Attachments
(1 file)
56.15 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150311030203 Steps to reproduce: 1. Go to https://web.whatsapp.com/ 2. Get phone to scan the QR to login 3. Got unresponsive script alert: Script: https://web.whatsapp.com/crypt…bfc74e221521a.js line 2 > eval:172 Actual results: Got unresponsive script alert: Script: https://web.whatsapp.com/crypt…bfc74e221521a.js line 2 > eval:172 Expected results: The login works fine on release channel.
Comment 1•9 years ago
|
||
The unresponsive script error happens whether you try to login or not.
Status: UNCONFIRMED → NEW
Component: Untriaged → JavaScript Engine
Ever confirmed: true
Product: Firefox → Core
Updated•9 years ago
|
OS: Windows 8.1 → All
Comment 2•9 years ago
|
||
Same issue in Mac OS X 10.10.3 also. Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0 ID:20150311030203 CSet: fd8e079d6335
Reporter | ||
Comment 3•9 years ago
|
||
Good on 03-07 nightly Bad on 03-08 nightly
![]() |
||
Comment 4•9 years ago
|
||
Should retest once we land all the bits blocking bug 1113369.
Blocks: 1113369
Comment 5•9 years ago
|
||
I hit this slow script error on http://boardgamegeek.com. I bisected this regression to the pushlog with bug 1113369: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=e42a8febca65&tochange=62fecc6ab96e
Keywords: regression,
reproducible
Reporter | ||
Comment 6•9 years ago
|
||
Confirmed fixed on 03-12 nightly
![]() |
||
Comment 7•9 years ago
|
||
Great, thanks!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 8•9 years ago
|
||
I verified that boardgamegeek.com no longer hangs the browser in Nightly 38 build 2015-03-13.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•