Open
Bug 1254621
Opened 9 years ago
Updated 3 years ago
Investigate thread_info time under AutoStopWatch constructor
Categories
(Core :: DOM: Core & HTML, defect, P5)
Core
DOM: Core & HTML
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox48 | --- | affected |
People
(Reporter: bzbarsky, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: btpp-fixlater)
The profile for bug 1254240, if I'm not misreading it, shows us taking a while under the AutoStopWatch constructor. Specifically, that constructor calls nsPerformanceStatsService::StopwatchStartCallback, which calls nsPerformanceStatsService::StopwatchStart, which calls thread_info, thread_self_trap, mach_port_deallocate, all of which take noticeable amounts of time. The thread_info call takes about 2/3 of the time under AutoStopWatch(), which is itself about 1/4 of the time under JS::Call in this case, afaict.
|
||
Updated•9 years ago
|
Whiteboard: btpp-fixlater
|
||
Updated•7 years ago
|
Priority: -- → P5
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•