On 7/16/2014 4:49 PM, Randell Jesup wrote:
On 7/16/2014 3:33 PM, Benjamin Smedberg wrote:
To round out the loop on this: I filed additional breakdown bugs on
the crash reporting stuff. See
https://bugzilla.mozilla.org/showdependencytree.cgi?id=1009760&hide_resolved=1
I have taken bug 1039
On Wednesday, July 16, 2014 10:49:40 PM UTC+2, Randell Jesup wrote:
> The other part is figuring out *when* to fire the plugin-failed event.
>
> Do we have heuristics for detecting crashed or hung plugins I can leverage?
Shouldn't things get kicked off via |ActorDestroy| with the |AbnormalShutd
On 7/16/2014 3:33 PM, Benjamin Smedberg wrote:
To round out the loop on this: I filed additional breakdown bugs on
the crash reporting stuff. See
https://bugzilla.mozilla.org/showdependencytree.cgi?id=1009760&hide_resolved=1
I have taken bug 1039575/bug 1039577/bug 1039579 in order to get a
On 7/15/2014 6:10 PM, Maire Reavy wrote:
On 7/15/2014 5:55 PM, Randell Jesup wrote:
On 7/15/2014 5:00 PM, Benjamin Smedberg wrote:
On 7/15/2014 4:58 PM, Felipe Gomes wrote:
Sounds good, but then it will always use the infobar. Are they
fundamentally unable to fire at a particular ?
Yes. The
On 7/15/2014 5:55 PM, Randell Jesup wrote:
On 7/15/2014 5:00 PM, Benjamin Smedberg wrote:
On 7/15/2014 4:58 PM, Felipe Gomes wrote:
Sounds good, but then it will always use the infobar. Are they
fundamentally unable to fire at a particular ?
Yes. There is no , just a JS API for webrtc.
RTCP
On 7/15/2014 5:00 PM, Benjamin Smedberg wrote:
On 7/15/2014 4:58 PM, Felipe Gomes wrote:
Sounds good, but then it will always use the infobar. Are they
fundamentally unable to fire at a particular ?
Yes. There is no , just a JS API for webrtc.
RTCPeerConnection is new'd, but is connected to
On 7/15/2014 4:58 PM, Felipe Gomes wrote:
Sounds good, but then it will always use the infobar. Are they fundamentally unable
to fire at a particular ?
Yes. There is no , just a JS API for webrtc.
--BDS
___
dev-media mailing list
dev-media@lists.mo
jamin Smedberg"
To: "Felipe Gomes" , "Eric Rescorla"
Cc: dev-media@lists.mozilla.org, "Georg Fritzsche"
Sent: Tuesday, July 15, 2014 5:49:11 PM
Subject: Re: GMP crash reporting update (schedule slip likely)
On 7/15/2014 4:41 PM, Felipe Gomes wrote:
> Ideally
On 7/15/2014 4:41 PM, Felipe Gomes wrote:
Ideally, on a crash, the plugin code should send a PluginCrashed event, one per
plugin instance, which is how it's done for the NPAPI plugins. Do these new
plugins use nsPluginHost et. al.?
No. They don't use nsPluginHost and they don't use
nsObjectL
ce/content/base/src/nsObjectLoadingContent.cpp#309
- Original Message -
From: "Eric Rescorla"
To: "Benjamin Smedberg"
Cc: dev-media@lists.mozilla.org, "Felipe Gomes" , "Georg
Fritzsche"
Sent: Tuesday, July 15, 2014 5:34:23 PM
Subject: Re: GMP cra
On Tue, Jul 15, 2014 at 1:19 PM, Benjamin Smedberg
wrote:
> The bug for hooking up crash reporting for GMP plugins is likely to slip
> past this week, and I'd like to talk about how to reduce risk there.
>
> Part of the problem is that I may not have broken that bug down
> sufficiently. There's r
.
- Original Message -
From: "Benjamin Smedberg"
To: dev-media@lists.mozilla.org, "Felipe Gomes"
Cc: "Georg Fritzsche"
Sent: Tuesday, July 15, 2014 5:19:37 PM
Subject: GMP crash reporting update (schedule slip likely)
The bug for hooking up crash reporting for
The bug for hooking up crash reporting for GMP plugins is likely to slip
past this week, and I'd like to talk about how to reduce risk there.
Part of the problem is that I may not have broken that bug down
sufficiently. There's really two parts to the problem: associating a GMP
crash with one
13 matches
Mail list logo