Loop client blocks(?) plugin crash reporter

RESOLVED INCOMPLETE

Status

P3
normal
Rank:
38
RESOLVED INCOMPLETE
4 years ago
2 years ago

People

(Reporter: drno, Unassigned)

Tracking

unspecified
All
Mac OS X
Points:
---
Bug Flags:
firefox-backlog +

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
I tried a couple of H264 calls with the Loop client (chatbox). The OpenH264 plugin kept crashing, which went unnoticed because I never saw the yellow notification bar at the top.
Only when I went onto the webrtc-landing pages to try a H264 loopback call, I saw the yellow plugin crash notification come up. And after that about:crashes showed a whole list of crashes in the plugin for the Loop calls I tried before.
(Reporter)

Comment 1

4 years ago
This was with 36.0a2 (2015-01-12) on Mac OSX 10.6 32bit.
Nils/Maire, how can we for an OpenH264 call in Loop?

I suspect we're not getting this notification as the platform code isn't set up for it.

My guess is that we'd need to punch a notification into the content space for when the plugin fails, and show the something went wrong message.
Flags: needinfo?(mreavy)
Flags: needinfo?(drno)
Priority: -- → P3
Hardware: x86 → All
To force Openh264, you have to add a pref to about:config. Add the pref media.navigator.video.preferred_codec as an integer and set it to 126.
Flags: needinfo?(mreavy)
(Reporter)

Comment 4

4 years ago
See Maire's description. Check in about:webrtc the SDP to verify that you got H264 (if you don't simply notice it by the quality of the picture ;-) ).

BTW my comment #1 was not 100% correct. I actually got the crashes, because I was using a 32bit plugin in a 64bit process. But that is probably a very good way to reliably reproduce crashes of the plugin.
Flags: needinfo?(drno)

Updated

4 years ago
backlog: --- → Fx38+
Rank: 38

Updated

4 years ago
backlog: Fx38+ → backlog+
Flags: firefox-backlog+
Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.