Closed
Bug 814699
Opened 12 years ago
Closed 12 years ago
WebRTC crash [@webrtc::ACMOpus::InternalInitDecoder]
Categories
(Core :: WebRTC: Audio/Video, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: posidron, Assigned: jesup)
References
Details
(Keywords: crash, testcase, Whiteboard: [WebRTC],[blocking-webrtc+] [qa-])
Crash Data
Attachments
(1 file)
61.04 KB,
text/plain
|
Details |
This is a first try of fuzzing RTP. The callstack file includes information about the intercepted packets, 'bt' and 'bt full'. The seed value shall be able to reproduce it. I will make the patch available after some tuning / reviews and probably add it to the WebRTC fuzzing meta-bug.
Reporter | ||
Comment 1•12 years ago
|
||
Assertion failed: (_decoderInstPtr == NULL), function InternalInitDecoder, file /Users/cdiehl/Code/Mozilla/mc-debug/media/webrtc/trunk/src/modules/audio_coding/main/source/acm_opus.cc, line 210
Updated•12 years ago
|
Crash Signature: [@ webrtc::ACMOpus::InternalInitDecoder]
Comment 2•12 years ago
|
||
Comment on attachment 684702 [details]
callstack
This particular issue will be fixed by the CL in <http://review.webrtc.org/933022/>, though it may be indicative of larger problems.
Updated•12 years ago
|
Flags: in-testsuite?
Comment 3•12 years ago
|
||
Christoph, do you have any testcase or not? Would be nice if you could mention that when you file a bug.
Reporter | ||
Comment 4•12 years ago
|
||
I wrote, I will make the patch available soon after some tuning / reviews and will attach it to the WebRTC fuzzing meta-bug. The seed value is printed in the callstack.
You later need just to enter the seed value as an environment variable to reproduce.
Comment 5•12 years ago
|
||
(In reply to Christoph Diehl [:cdiehl] from comment #4)
> I wrote, I will make the patch available soon after some tuning / reviews
> and will attach it to the WebRTC fuzzing meta-bug. The seed value is printed
> in the callstack.
> You later need just to enter the seed value as an environment variable to
> reproduce.
It would be great if you can give the information on that bug to lower the amount of confusion and reduce the search time. A link to the appropriate comment in the other bug would be enough. Thanks.
Assignee | ||
Updated•12 years ago
|
Whiteboard: [WebRTC],[blocking-webrtc+]
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → rjesup
Depends on: webrtc_updates
Assignee | ||
Comment 6•12 years ago
|
||
Fixed by the webrtc.org checkin for 3.20 (bug 830247)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Flags: in-testsuite? → in-testsuite-
Whiteboard: [WebRTC],[blocking-webrtc+] → [WebRTC],[blocking-webrtc+] [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•