For bug1305341 I tested WebRTC on Yocto 2.1 on Wandboard. I used an UVC video camera. * Wandboard: http://www.wandboard.org/ * Yocto on Wandboard: http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard * Firefox recipe: https://github.com/mozilla-japan/meta-browser I built Firefox with WebRTC support. When I start Firefox Hello or any other WebRTC services the camera device is recognized and it appears on the device list. But when I try to start video chat, the browser crashes. I don't investigate the detail yet. On Ubuntu 14.04 on PC I succeeded to use WebRTC with almost same mozconfig. I should get more information from the device and other environments.
OS: Unspecified → Linux
Hardware: Unspecified → ARM
We'd need a crash stack at minimum to start with. You can also run with MOZ_LOG=MediaManager:4,GetUserMedia:4,webrtc_trace:65535,signaling:4 WEBRTC_TRACE_FILE=nspr and collect logs
backlog: --- → parking-lot
In addition, I got the following console message: mmap() failed: Cannot allocate memory mmap() failed: Cannot allocate memory ... mmap() failed: Cannot allocate memory mmap() failed: Cannot allocate memory out of memory: 0x0000000000151800 bytes requested Segmentation fault
But when I run firefox on GDB, the issue doesn't reproduce (WebRTC works fine). The stack trace is taken from a core file.
The camera device I used: Logicool C910 & C920
(In reply to Takuro Ashie from comment #6) > The camera device I used: Logicool C910 & C920 Logicool is apparently what Logitech is known as in Japan and maybe elsewhere
The stack trace is a crash in Garbage Collection code. This implies some type of memory corruption. Note: I test with a c920 camera frequently, as do others. You may need to build an ASAN build using clang track this down, if that will work on your platform. https://developer.mozilla.org/en-US/docs/Mozilla/Testing/Firefox_and_Address_Sanitizer
It works with recent code: https://github.com/webdino/meta-browser/tree/firefox-52esr https://github.com/webdino/meta-browser/tree/firefox-60esr
Status: NEW → RESOLVED
Last Resolved: 3 days ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.