Closed
Bug 1836508
Opened 11 months ago
Closed 7 months ago
Handle writing of dom::Performance entries when OnStopRequest is moved OMT
Categories
(Core :: Networking: HTTP, task, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: acreskey, Unassigned)
References
Details
(Whiteboard: [necko-triaged])
If we retarget OnStopRequest OMT, then we run into problems writing the dom::Performance
entries.
Called through this path:
LoadInfo::GetPerformanceStorage()
mozilla::net::HttpBaseChannel::MaybeReportTimingData()
mozilla::net::HttpChannelChild::DoPreOnStopRequest()
Problems encountered so far:
-
A call to
nsGlobalWindowInner::GetInnerWindowWithId
which is main-thread only. -
In general mozilla::dom::Performance looks to be intended for main-thread only.
We potentially create the object OMT and also add performance entries.
The writing to the performance object may need to be deferred or added as a main thread task.
Updated•7 months ago
|
Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•