Closed Bug 811184 Opened 13 years ago Closed 13 years ago

WebRTC crash [@PL_ArenaAllocate]

Categories

(Core :: WebRTC: Signaling, defect, P2)

Product:
Core
Component:
WebRTC: Signaling
Platform:
x86_64
macOS
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 811183
Tracking Flags:
Tracking Status
firefox16 --- unaffected
firefox17 --- unaffected
firefox-esr10 --- unaffected

People

(Reporter: ekr, Unassigned)

References

Details

(Keywords: crash, sec-critical, testcase, Whiteboard: [WebRTC], [blocking-webrtc+] [qa verification blocked])

+++ This bug was initially created as a clone of Bug #800969 +++ The testcase must not be opened over the command-line via GDB else it will produce an assertion failure: (mod != NULL, at pk11slot.c:1766). Instead drag & drop the testcase into Firefox. Reason: KERN_PROTECTION_FAILURE at address: 0x00000001304c3eb8 [Switching to process 63747 thread 0x3907] PL_ArenaAllocate (pool=<value temporarily unavailable, due to optimizations>, nb=<value temporarily unavailable, due to optimizations>) at /Users/cdiehl/Code/Mozilla/mc-inbound-asan/nsprpub/lib/ds/plarena.c:170 170 if ( PR_FAILURE == LockArena()) mozilla-inbound changeset: 110109:78f0949318a5 tag: tip
Got a stack? or is that it?
Flags: in-testsuite-
ekr: What is this bug actually? Does it refer to a specific comment/attachment in bug 800969? Do we know what versions this affects? Stack?
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
I'm removing the tracking flags as bug 811183 has them anyhow.
status-firefox18: affected → ---
status-firefox19: affected → ---
tracking-firefox18: + → ---
tracking-firefox19: + → ---
Group: core-security
You need to log in before you can comment on or make changes to this bug.