[10.9] crash in libdispatch

RESOLVED WORKSFORME

Status

()

Core
General
--
critical
RESOLVED WORKSFORME
5 years ago
4 years ago

People

(Reporter: Scoobidiver (away), Unassigned)

Tracking

(Blocks: 1 bug, {crash})

Trunk
x86_64
Mac OS X
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

5 years ago
There are a few crashes on Mac OS X 10.9.

Signature 	libdispatch.dylib@0x6091 More Reports Search
UUID	3225abd3-5d25-4eed-b1ab-9fe1f2130623
Date Processed	2013-06-23 01:40:23
Uptime	2379
Last Crash	more than 3 months before submission
Install Age	10.9 hours since version was first installed.
Install Time	2013-06-22 14:43:12
Product	Firefox
Version	24.0a1
Build ID	20130622031042
Release Channel	nightly
OS	Mac OS X
OS Version	10.9.0 13A476u
Build Architecture	amd64
Build Architecture Info	family 6 model 37 stepping 5
Crash Reason	EXC_BAD_ACCESS / KERN_INVALID_ADDRESS
Crash Address	0x6b3de0
App Notes 	
AdapterVendorID: 0x10de, AdapterDeviceID: 0x a29GL Layers! GL Context? GL Context+ GL Layers+ 
Processor Notes 	sp-processor05_phx1_mozilla_com_25008:2012; exploitability tool: ERROR: unable to analyze dump
EMCheckCompatibility	False
Adapter Vendor ID	0x10de
Adapter Device ID	0x a29

Frame 	Module 	Signature 	Source
0 	libdispatch.dylib 	libdispatch.dylib@0x6091 	
1 	CoreFoundation 	CoreFoundation@0xef5f2 	
2 	CoreFoundation 	CoreFoundation@0x88300 	
3 	CoreFoundation 	CoreFoundation@0x87360 	
4 	libobjc.A.dylib 	libobjc.A.dylib@0x1d658 	
5 	libobjc.A.dylib 	libobjc.A.dylib@0x70b9 	
6 	CoreFoundation 	CoreFoundation@0x92f9 	
7 	CoreFoundation 	CoreFoundation@0x2d38d 	
8 	CoreFoundation 	CoreFoundation@0x87d4c 	
9 	CoreFoundation 	CoreFoundation@0x92f9 	
10 	HIServices 	HIServices@0xd4b6 	
11 	CoreFoundation 	CoreFoundation@0x86f8b 	
12 	HIServices 	HIServices@0x4c88 	
13 	HIServices 	HIServices@0xce79 	
14 	HIServices 	HIServices@0x29fe7 	
15 	HIServices 	HIServices@0x2aa2a 	
16 	AppKit 	AppKit@0x76b1ff 	
17 	AppKit 	AppKit@0x76b234 	
18 	AppKit 	AppKit@0x76b369 	
19 	AppKit 	AppKit@0xa8f7dd 	
20 	AppKit 	AppKit@0x5a1ce0 	
21 	AppKit 	AppKit@0x59f069 	
22 	CoreFoundation 	CoreFoundation@0xf129d 	
23 	AppKit 	AppKit@0x59f059 	
24 	CoreFoundation 	CoreFoundation@0xe7f7f 	
25 	CoreFoundation 	CoreFoundation@0x3459 	
26 	CoreFoundation 	CoreFoundation@0x318e 	
27 	CoreFoundation 	CoreFoundation@0xcc19 	
28 	CoreFoundation 	CoreFoundation@0xcdc6a 	
29 	libmozglue.dylib 	ozone_size 	memory/mozjemalloc/jemalloc.c:7003
30 	CoreFoundation 	CoreFoundation@0x2f383 	
31 	firefox 	main 	browser/app/nsBrowserApp.cpp:181
32 	CoreFoundation 	CoreFoundation@0x2e7b3 	

More reports at:
https://crash-stats.mozilla.com/report/list?signature=libdispatch.dylib%400x6091

Comment 1

5 years ago
(In reply to Scoobidiver from comment #0)
> Install Age	10.9 hours since version was first installed.

Intentional? :D
(Reporter)

Comment 2

5 years ago
(In reply to Florian Bender from comment #1)
> > Install Age	10.9 hours since version was first installed.
> Intentional? :D
10.9 hours means 10:54 and consistent with Install Time: 2013-06-22 14:43:12.
This is likely an Apple bug.

With luck it also effects Safari (or other Apple apps), and will get fixed in a future developer seed of OS X 10.9.
(Reporter)

Updated

5 years ago
Crash Signature: [@ libdispatch.dylib@0x6091] → [@ libdispatch.dylib@0x6091] [@ libdispatch.dylib@0x5db1]
I see 6 of these over the last month -- but all in build 13A497d, which isn't the current DP.

(As of today, DP7 (build 13A569) is the current one.)
I see two crashes with this signature in the last 28 days; one in Fx 24.0, another in Fx 23.0.1. What's the state of this crash in current branches?
I see six of these over the last 4 weeks, all in older DPs of OS X 10.9 (all older than DP7):

bp-d2a78a55-3339-430d-b658-7d3452130930
bp-4a162723-3a21-490e-82ed-dc49b2130930
bp-4bb15692-9c2c-48dc-929f-c171d2130924
bp-c997953c-7601-45c9-a362-65adb2130918
bp-bdb27e91-0e99-45e5-bf45-c16132131001
bp-cb12eb17-9c7a-44a6-b948-6c7402130926

So this is presumably an Apple bug that Apple has fixed.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.