Closed
Bug 1337080
Opened 8 years ago
Closed 6 years ago
Switch GMP initialization to be asynchronous
Categories
(Core :: Audio/Video: GMP, defect, P4)
Core
Audio/Video: GMP
Tracking
()
RESOLVED
WONTFIX
Performance Impact | low |
People
(Reporter: ehsan.akhgari, Assigned: cpearce)
References
(Blocks 1 open bug)
Details
(Keywords: perf)
PGMPService::Msg_LaunchGMP can take a long time:
<https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2017-02-05&keys=PGMPService%253A%253AMsg_LaunchGMP!PContent%253A%253AMsg_RpcMessage!PContent%253A%253AMsg_GetGfxVars!PAPZCTreeManager%253A%253AMsg_ReceiveMouseInputEvent&max_channel_version=nightly%252F54&measure=IPC_SYNC_LATENCY_MS&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2017-02-02&table=0&trim=1&use_submission_date=0>
Start End IPC_SYNC_LATENCY_MS Count
0 1 0 (0%)
1 3 2.13k (27.11%)
3 8 270 (3.44%)
8 20 130 (1.66%)
20 50 1.16k (14.72%)
50 126 2.39k (30.44%)
126 317 891 (11.35%)
317 796 529 (6.74%)
796 2k 263 (3.35%)
2k Infinity 94 (1.2%)
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → cpearce
Priority: -- → P1
Assignee | ||
Comment 1•8 years ago
|
||
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?
Reporter | ||
Comment 2•8 years ago
|
||
(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]
Assignee | ||
Comment 4•8 years ago
|
||
Since this is off-main-thread, I'm de-prioritizing this to P3.
Priority: P1 → P3
Comment 5•7 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Assignee | ||
Comment 6•6 years ago
|
||
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: 6 years ago
Resolution: --- → WONTFIX
Updated•3 years ago
|
Performance Impact: --- → P3
Whiteboard: [qf:p3]
You need to log in
before you can comment on or make changes to this bug.
Description
•