Closed Bug 1836508 Opened 2 years ago Closed 2 years ago

Handle writing of dom::Performance entries when OnStopRequest is moved OMT

Categories

(Core :: Networking: HTTP, task, P3)

Product:
Core
Component:
Networking: HTTP
Platform:
All
Unspecified
Type:
task

Tracking

()

Status:
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:

  1. A call to nsGlobalWindowInner::GetInnerWindowWithId which is main-thread only.

  2. 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.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.