Closed
Bug 522354
Opened 15 years ago
Closed 6 years ago
investigate why we spend a long time js_execute()ing things
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: taras.mozilla, Assigned: sayrer)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [ts])
No description provided.
Reporter | ||
Updated•15 years ago
|
Whiteboard: [ts]
Assignee | ||
Updated•15 years ago
|
Assignee: general → sayrer
Assignee | ||
Comment 1•15 years ago
|
||
still need the input files here
Reporter | ||
Comment 2•15 years ago
|
||
This is hard to reduce. I tried making a purejs version of nsExtensionManager.js, but it js_executed 5x faster than the one in the code. I'm begining to wonder if this is to due with what bug 459117 would address. Ie various Ci.fooInterface, etc mentions in the toplevel trigger xpconnect overhead. http://mxr.mozilla.org/mozilla-central/source/js/src/xpconnect/loader/mozJSComponentLoader.cpp#1395 is the js_execute that's taking a while.
Comment 3•15 years ago
|
||
Taras, what does a TMFLAGS=abort log in a debug build have to say about nsExtensionManager.js, if anything?
Comment 4•6 years ago
|
||
Closing stale performance bug as INCOMPLETE.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•