1191222 - crash in CoreFoundation@0x184ce

Status: RESOLVED WORKSFORME

(Core :: Graphics: Layers, defect)

Description

[Schalk Neethling [:espressive]]

This bug was filed from the Socorro interface and is 
report bp-18a0345c-4bd9-4f86-9744-a99b82150803.
=============================================================

Comment 1

[u279076]

Stack:
0 	CoreFoundation 	CoreFoundation@0x184ce 	
Ø 1 	CoreFoundation 	CoreFoundation@0x3ab24 	
Ø 2 	CoreFoundation 	CoreFoundation@0x29f8d 	
Ø 3 	CoreFoundation 	CoreFoundation@0x29d73 	
Ø 4 	CoreFoundation 	CoreFoundation@0x1804a 	
Ø 5 	VideoDecodeAcceleration 	VideoDecodeAcceleration@0x7ff 	
Ø 6 	VideoToolbox 	VideoToolbox@0xf86c 	
Ø 7 	VideoToolbox 	VideoToolbox@0x101dc 	
Ø 8 	VideoToolbox 	VideoToolbox@0x101a3 	
Ø 9 	VideoToolbox 	VideoToolbox@0x103b1 	
Ø 10 	CoreMedia 	CoreMedia@0x3a5ed 	
11 	libsystem_pthread.dylib 	_pthread_body 	
12 	libsystem_pthread.dylib 	_pthread_start 	
13 	libsystem_pthread.dylib 	thread_start 	

More reports:
https://crash-stats.mozilla.com/report/list?product=Firefox&signature=CoreFoundation%400x184ce

Severity:
Using super search I'm able to determine that these crashes seem to be completely isolated to Firefox 39. I see no crashes with earlier or more recent versions over the last six months. Looking at the topcrash report this first showed up on May 2nd, 2015 and is the 105th ranked topcrash for Mac OS X, not having changed by any significant margin in volume.

Platform:
100% of the crashes are on Mac OS 10.10 so it seems other OS X versions are unaffected. 

Uptime:
48% of the crashes happen within the first 5 minutes.
36% of the crashes happen after an hour or more of uptime.
 6% of the crashes happen between 5 to 15 minutes of uptime.

Cases:
The majority of comments mention trying to play video on Youtube which seems to be backed up by the predominance of youtube.com in the URLs reported.

Comment 2

[u279076]

[Tracking Requested - why for this release]: Nominating to track just to increase Release Management's awareness. Given the data we have about this crash I'm not sure there's anything we can do before the release next week, nor will this be of any concern once we release. FWIW, this may be an Apple bug but that's just wild speculation on my part.

Comment 3

[Jean-Yves Avenard [:jya]]

My guess was that this was a bug in 10.10 ; reports that it stopped when people update to 10.10.1