1074017 - [EME] Better debug facilities for GMP developers

Status: RESOLVED INACTIVE

(Core :: Audio/Video: Playback, defect)

Description

[Chris Pearce [:cpearce (Not reading bugmail)]]

We should add debugging tools to make it easier for GMP developers.

* Ability to set a breakpoint when the GMP child process starts up, so that devs can connect debugger to the process before it starts executing code.
* More logging to diagnose MediaKeys creation/other failures. Just rejecting a promise is not very helpful. We can log these to the browser console.

Comment 1

[Chris Pearce [:cpearce (Not reading bugmail)]]

Another idea: compare the GMP APIs that a GMP says is supports in its .info file with a whilelist which matches our GMP_API_* macros, and log a message to the Browser Console and to NSPR logs if a plugin reports that it supports an API that Gecko does not.

Comment 2

[Chris Pearce [:cpearce (Not reading bugmail)]]

(In reply to Chris Pearce (:cpearce) from comment #1)
> Another idea: compare the GMP APIs that a GMP says is supports in its .info
> file with a whilelist which matches our GMP_API_* macros, and log a message
> to the Browser Console and to NSPR logs if a plugin reports that it supports
> an API that Gecko does not.

Spun this off into bug 1121154, as I think we need it for matching different plugin versions against different Gecko versions.

Comment 3

[Chris Pearce [:cpearce (Not reading bugmail)]]

Very nice to have, but given Adobe are mostly done with developing their GMP a bit "too little, too late"... So unblocking.

Comment 4

[Nils Ohlmeier [:drno]]

Mass closing do to inactivity.
Feel free to re-open if still needed.