Closed
Bug 949878
Opened 11 years ago
Closed 11 years ago
Rooting hazard analysis timeouts
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla29
People
(Reporter: sfink, Assigned: sfink)
References
Details
(Whiteboard: [qa-])
Attachments
(1 file)
1.65 KB,
patch
|
terrence
:
review+
|
Details | Diff | Splinter Review |
When h4writer pushed bug 939614 this morning, suddenly the SM(Hf) static rooting analysis became insanely slow. Where before it took 10 minutes to load the callgraph, it started taking over an hour (and getting killed for nonresponsiveness). I still don't know why that patch triggered it, but the slowness is due to bug 949724.
Assignee | ||
Comment 1•11 years ago
|
||
Fortunately, the workaround is trivial. With this patch, bug 939614 completes the analysis run just fine. (The computeGCFunctions phase drops from its usual 10 min to about 1 minute.)
Attachment #8347026 -
Flags: review?(terrence)
Comment 2•11 years ago
|
||
Comment on attachment 8347026 [details] [diff] [review] Switch to integer indexes to avoid pathological array slowdown Review of attachment 8347026 [details] [diff] [review]: ----------------------------------------------------------------- Great! r=me This is a great real-world stress test for our array machinery. Could you file a followup bug to make this workload into a benchmark?
Attachment #8347026 -
Flags: review?(terrence) → review+
Assignee | ||
Comment 3•11 years ago
|
||
(In reply to Terrence Cole [:terrence] from comment #2) > This is a great real-world stress test for our array machinery. Could you > file a followup bug to make this workload into a benchmark? That's bug 949724.
Assignee | ||
Comment 4•11 years ago
|
||
http://hg.mozilla.org/integration/mozilla-inbound/rev/52a6e01a91d9
Comment 5•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/52a6e01a91d9
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
Updated•10 years ago
|
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•