Closed
Bug 549540
Opened 14 years ago
Closed 13 years ago
use jshashtable instead of jsdhash for js_SweepAtomState
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 581875
People
(Reporter: gal, Unassigned)
References
Details
shark sees a bunch of integer multiplications in js_SweepAtomState. Should be investigated. This is a couple percent (2-4%) of total GC/CC time. JS_DHashTableEnumerate is the offender.
|
||
Updated•14 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
|
|
||
Updated•14 years ago
|
Summary: use luke's hash table for js_SweepAtomState → use jshashtable instead of jsdhash for js_SweepAtomState
|
||
Comment 1•13 years ago
|
||
Looks like this change has been made. I can't find the bug that did it, so I'm going to close this instead of dupe it.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
|
Reporter | |
Comment 2•13 years ago
|
||
You can go to a source line inside the change and then do hg blame. That will point you to a change set. If thats not the one, you can search for change sets before that change set for the same line. That way you should find the patch that fixed this (WFM is good enough too though).
You need to log in
before you can comment on or make changes to this bug.
Description
•