Closed
Bug 840112
Opened 11 years ago
Closed 3 years ago
javascript causes spinlock/unresponsive after window is maximized due to js::array_concat
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: wmiler, Unassigned)
References
Details
(Keywords: hang)
Attachments
(1 file)
148.32 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:20.0) Gecko/20130210 Firefox/20.0 Build ID: 20130210042017 Steps to reproduce: Minimized window previous evening, expanded window back to normal. Actual results: Browser opens up, and immediately goes into spinlock/unresponsiveness.
Comment 1•11 years ago
|
||
Which JavaScript?
Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Aleksej [:Aleksej] from comment #1) > Which JavaScript? What ever is compiled into the Aurora (20 branch)? Otherwise I don't understand your question.
Severity: critical → normal
Reporter | ||
Updated•11 years ago
|
Severity: normal → critical
Comment 3•11 years ago
|
||
Have you experienced this again since the first time ?
Reporter | ||
Comment 4•11 years ago
|
||
I'm thinking this is related to https://bugzilla.mozilla.org/show_bug.cgi?id=778599 The particular point at which it hangs has moved over to js::NewDenseCopiedArray which is within the above mentioned bug.
See Also: → 778599
Updated•11 years ago
|
Assignee: nobody → general
Component: Untriaged → JavaScript Engine
Product: Firefox → Core
Comment 5•11 years ago
|
||
Yeah, that does look similar. Do you leave Facebook open for long periods of time? For me, reloading the FB tab would make the problem go away.
Summary: javascript causes spinlock/unresponsive after window is maximized → javascript causes spinlock/unresponsive after window is maximized due to js::array_concat
Comment 6•11 years ago
|
||
As I said in the other bug: If the concat's spinning on NewDenseCopiedArray a lot, that's because (window[x] || []) has a very large dense initialized length, which means window[x] is likely a very large array. Smells like a TE bug to me, that whatever's being fed in there isn't being cleared out correctly over time or something. The value of |x| in that case would probably be informative to a FB engineer.
Comment 7•11 years ago
|
||
Left Firefox minimized for couple of hours on Facebook - didn't see any issues, the CPU usge was low. nightly 2013-06-04, mac os x 10.8.3
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
set as resolved incomplete as the user is disabled.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•