Closed Bug 389345 Opened 17 years ago Closed 7 years ago

XPCTools JS profiler returns nonsensical results for "time spent in function itself"

Categories

(Core :: XPConnect, defect)

Product:
Core
Component:
XPConnect
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: myk, Unassigned)

Details

In a recent profile of the startup process (bug 385224, attachment 273289 [details]), the XPCTools JavaScript profiler reported nonsensical "time spent in function itself" results for most of the functions I looked at.

The numbers should be in the low single or double-digits for most functions, but instead they're values like 4294967295 and 2341572797.  Only a few functions were reported to have sensible times like 0 or 18 (ms).
Currently, because of this bug, we have to manually follow entrainment chains to figure out which functions actually had a cost.  Fixing this bug would make it much easier to identify those functions, so it'd be great to have a fix for this during the performance optimization work we do in the 1.9 cycle.
Flags: blocking1.9?
Not a blocker for the release. Would take a patch if a safe one was made though.
Flags: blocking1.9? → blocking1.9-
XPCTools doesn't seem to exist any more.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.