Closed
Bug 1362109
Opened 8 years ago
Closed 8 years ago
Use the parent process's startTime when dumping content process profiles
Categories
(Core :: Gecko Profiler, enhancement)
Core
Gecko Profiler
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mstange, Unassigned)
Details
At the moment, each process has a different profiler startTime, and perf.html has to look at each process's profile.meta.startTime and adjust all time values in the subprocess profile.
It would be nice if Gecko could do this adjustment itself.
Reporter | ||
Updated•8 years ago
|
Assignee: mstange → nobody
Reporter | ||
Comment 1•8 years ago
|
||
When I filed this bug I was assuming that we were storing TimeStamp values in the buffer and in the markers, but that's not true. We store "double" values, which are computed as (time - CorePS::ProcessStartTime()).ToMilliseconds(). And it would be hard to get the parent process startup time as a TimeStamp during profiler_init in the content process.
I'm thinking that this bug may not be worth spending time on.
You need to log in
before you can comment on or make changes to this bug.
Description
•