Closed
Bug 1061765
Opened 10 years ago
Closed 10 years ago
Reused call crashed both participants | crash in libsystem_c.dylib@0x1d70 | getDeviceNamesFromIndex | memset
Categories
(Core :: WebRTC, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1061475
People
(Reporter: Felipe, Unassigned)
Details
(Keywords: crash, reproducible)
Crash Data
This bug was filed from the Socorro interface and is
report bp-4e939675-40c4-4841-86d1-0f1112140902.
=============================================================
STR:
- User A generated a link to invite someone to talk
- User B clicked the link, both accepted the video call and it worked properly.
- After the call had finished, User B reused the link and clicked the Call button again and that crashed his Firefox
- But before crashing, that generated the call request to User A. User A then accepted the call and it crashed User A.
Comment 1•10 years ago
|
||
The crash report in comment 0 was for User A on 10.8.5.
The crash report for User B is on 10.9.4:
report bp-fc1f8bc1-9389-4487-8453-d8bab2140902.
with signature:
[@ libsystem_platform.dylib@0x4e75 ]
at -[VideoCaptureMacQTKitInfoObjC getDeviceNamesFromIndex:DefaultName:WithLength:AndUniqueID:WithLength:AndProductID:WithLength:]
Group: core-security
Crash Signature: [@ libsystem_c.dylib@0x1d70] → [@ libsystem_c.dylib@0x1d70]
[@ libsystem_platform.dylib@0x4e75]
-[VideoCaptureMacQTKitInfoObjC getDeviceNamesFromIndex:DefaultName:WithLength:AndUniqueID:WithLength:AndProductID:WithLength:]
Summary: Reused call crashed both participants | crash in libsystem_c.dylib@0x1d70 → Reused call crashed both participants | crash in libsystem_c.dylib@0x1d70 | getDeviceNamesFromIndex | memset
Comment 2•10 years ago
|
||
Going to unhide this because both sides look like a null dereference. Hard to say if this is a problem in WebRTC or Loop's use of it (but probably WebRTC).
Updated•10 years ago
|
Group: core-security
Comment 3•10 years ago
|
||
Patch has already landed
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•