Closed Bug 1271167 Opened 10 years ago Closed 6 years ago

Crash on libunwind.dylib`libunwind::CompactUnwinder_x86_64<libunwind::LocalAddressSpace>::stepWithCompactEncodingFrameless

Categories

(Core :: Widget: Cocoa, defect, P5)

Unspecified
macOS
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: alwu, Unassigned)

Details

(Whiteboard: tpi:-)

Attachments

(1 file)

Can't run the nightly from today's build (changeset:296443:bae525a694e2) --- Process 50062 launched: '/Users/Alastor/build_mc_obj/dist/Nightly.app/Contents/MacOS/firefox' (x86_64) Process 50062 stopped * thread #1: tid = 0xb27f08, 0x00007fff8970ea81 libunwind.dylib`libunwind::CompactUnwinder_x86_64<libunwind::LocalAddressSpace>::stepWithCompactEncodingFrameless(unsigned int, unsigned long long, libunwind::LocalAddressSpace&, libunwind::Registers_x86_64&, bool) + 565, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT) frame #0: 0x00007fff8970ea81 libunwind.dylib`libunwind::CompactUnwinder_x86_64<libunwind::LocalAddressSpace>::stepWithCompactEncodingFrameless(unsigned int, unsigned long long, libunwind::LocalAddressSpace&, libunwind::Registers_x86_64&, bool) + 565 libunwind.dylib`libunwind::CompactUnwinder_x86_64<libunwind::LocalAddressSpace>::stepWithCompactEncodingFrameless(unsigned int, unsigned long long, libunwind::LocalAddressSpace&, libunwind::Registers_x86_64&, bool) + 565: -> 0x7fff8970ea81: movq (%rax), %rdx 0x7fff8970ea84: movq %rdx, 0x8(%rcx) 0x7fff8970ea88: jmp 0x7fff8970eab5 ; libunwind::CompactUnwinder_x86_64<libunwind::LocalAddressSpace>::stepWithCompactEncodingFrameless(unsigned int, unsigned long long, libunwind::LocalAddressSpace&, libunwind::Registers_x86_64&, bool) + 617 0x7fff8970ea8a: movq (%rax), %rdx
Attached file Crash stack
Component: General → Untriaged
Product: Firefox → Core
Component: Untriaged → Widget: Cocoa
BTW, I'm using OSX 10.9.5.
It seems that broke for a while.... because I can't run the nightly even I reverted my version to the changeset:296111.
Whiteboard: tpi:-
Decreasing the priority as no update for the last 2 years on this bug. See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage about the priority meaning.
Priority: P1 → P5

Are you still experiencing this issue?

Flags: needinfo?(alwu)

No, I haven't seen this issue for a long while.

Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(alwu)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: