Closed
Bug 481758
Opened 15 years ago
Closed 15 years ago
TM: need to trace 'new Array(4)' for crypto-aes
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 481754
People
(Reporter: dmandelin, Unassigned)
Details
Currently we're taking a 30ms hit running crypto-aes in the browser. Our shell score isn't that great either. It's not exactly clear what's causing the browser regression, but it seems to be related to the aborts. All the 'real' aborts are for the expression 'new Array(4)', which gives: abort: 6723: untraceable native Abort recording of tree crypto-aes.js:96 at crypto-aes.js:97: JSOP_NEW
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•