Closed Bug 1337080 Opened 7 years ago Closed 5 years ago

Switch GMP initialization to be asynchronous

Categories

(Core :: Audio/Video: GMP, defect, P4)

defect

Tracking

()

RESOLVED WONTFIX
Performance Impact low

People

(Reporter: ehsan.akhgari, Assigned: cpearce)

References

(Blocks 1 open bug)

Details

(Keywords: perf)

Assignee: nobody → cpearce
Priority: -- → P1
Note: we make the sync call to LaunchGMP on the GMP thread, not on the main message loop thread. Does that mean that the other threads involved in IPC and the main thread, aren't affected by this sync IPC message?
(In reply to Chris Pearce (:cpearce) from comment #1)
> Note: we make the sync call to LaunchGMP on the GMP thread, not on the main
> message loop thread. Does that mean that the other threads involved in IPC
> and the main thread, aren't affected by this sync IPC message?

I think so.  It's a bit annoying that these messages are all lumped into the same telemetry probe (for main thread vs non-main thread case.)
This doesn't block any main threads so it isn't urgent but it is possible for one GMP to block another.
Whiteboard: [qf:p3]
Since this is off-main-thread, I'm de-prioritizing this to P3.
Priority: P1 → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Keywords: perf

I'm going to WONTFIX this. Doing a sync launch on the GMP thread won't block other threads, so this should be benign.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Performance Impact: --- → P3
Whiteboard: [qf:p3]
You need to log in before you can comment on or make changes to this bug.