Crash in libc-2.19.so@0x35067
Categories
(Core :: WebRTC: Audio/Video, defect, P2)
Tracking
()
People
(Reporter: remi2402, Unassigned)
Details
Crash Data
This bug was filed from the Socorro interface and is
report bp-0b3512ff-1523-438e-b767-381ea0190107.
Top 10 frames of crashing thread:
0 libc-2.19.so libc-2.19.so@0x35067
1 libc-2.19.so libc-2.19.so@0x36447
2 libc-2.19.so libc-2.19.so@0x731b3
3 libc-2.19.so libc-2.19.so@0x165cb2
4 libc-2.19.so libc-2.19.so@0x165c9a
5 libc-2.19.so libc-2.19.so@0x165cb8
6 libc-2.19.so libc-2.19.so@0x165cc0
7 ld-2.19.so ld-2.19.so@0x996c
8 libc-2.19.so libc-2.19.so@0x165cc0
9 libc-2.19.so libc-2.19.so@0x72f9d
=============================================================
Hi,
I've had 3 successive crashes right after the update to 65b8 (up from 65b4 I think), and webrtc shows up in all 3:
- https://crash-stats.mozilla.com/report/index/bp-0b3512ff-1523-438e-b767-381ea0190107
- https://crash-stats.mozilla.com/report/index/bp-9a008471-55fd-41e9-a7a8-7f2140190107
- https://crash-stats.mozilla.com/report/index/bp-3ae1e36c-99eb-4dce-9a3e-31ba80190107
Note, I'm on Debian Jessie (current oldstable)
Comment 1•7 years ago
|
||
https://crash-stats.mozilla.com/search/?proto_signature=~webrtc%3A%3Avideocapturemodule%3A%3ADeviceInfoLinux%3A%3AEventCheck shows a bunch of other webrtc crashes in that area.
Updated•7 years ago
|
| Reporter | ||
Comment 2•6 years ago
|
||
Just had this again many times with 67b4 (https://crash-stats.mozilla.org/report/index/22ff3bd5-940c-48b9-997b-14a620190325 is the most recent crash) on the same jessie machine. Simply going to my gmail tab would reliably take down the whole browser after a few seconds. Since the crash report still mentioned webrtc, I googled around and disabled "media.peerconnection.enabled" in about:config, and that seems to prevent the crash.
I think I can live without webrtc (I don't do any conferencing), but knowing any website can crash my browser and potentially lose work is somewhat alarming.
Let me know if there's anything I can do to help diagnose this issue.
Thanks
Comment 3•6 years ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•