Closed Bug 1438909 Opened 8 years ago Closed 8 years ago

Crash in fglrx_dri.so@0x15cc349

Categories

(Core :: Security: Process Sandboxing, defect)

Unspecified
Linux
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1438215

People

(Reporter: mccr8, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-2443deb1-3e95-4eab-b80c-90c0f0180214. ============================================================= Top 10 frames of crashing thread: 0 fglrx_dri.so fglrx_dri.so@0x15cc349 1 libmozsandbox.so mozilla::SigSysHandler security/sandbox/linux/Sandbox.cpp:137 2 libmozsandbox.so mozilla::ContentSandboxPolicy::OpenTrap security/sandbox/linux/SandboxFilter.cpp:419 3 libmozsandbox.so sandbox::Trap::SigSys security/sandbox/chromium/sandbox/linux/seccomp-bpf/trap.cc:250 4 libmozsandbox.so mozilla::SigSysHandler security/sandbox/linux/Sandbox.cpp:137 5 fglrx_dri.so fglrx_dri.so@0x2210fdb 6 fglrx_dri.so fglrx_dri.so@0x2210fea 7 firefox arena_t::DallocRun 8 firefox free 9 fglrx_dri.so fglrx_dri.so@0x20cddb8 ============================================================= #5 Linux top crash for the 2-14 Nightly, with 14 crashes from 2 installations.
Any ideas, Jed?
Flags: needinfo?(jld)
(In reply to Andrew McCreight [:mccr8] from comment #0) > #5 Linux top crash for the 2-14 Nightly, with 14 crashes from 2 > installations. I accidentally included a 2-15 build in there, so this may not be accurate.
This looks like bug 1438215 — compare with the crash linked in bug 1438215 comment #2, and see also the real stack in bug 1438215 comment #3 (the sandbox-related addresses that Breakpad's stack scanning found appear to be from function activations that already returned). Although I didn't think that crash would happen without changing hidden prefs (or code) to allow access to /dev/ati/..., and I didn't think anyone besides gcp was trying that at the moment.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(jld)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.