Crash in pthread_mutex_lock | -[NSMutableArray sortUsingComparator:]

NEW
Unassigned

Status

()

Core
DOM: Device Interfaces
P3
critical
11 months ago
11 months ago

People

(Reporter: Jukka Jylänki, Unassigned)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

11 months ago
This bug was filed from the Socorro interface and is 
report bp-43779e95-aacb-4b29-80c3-072c80170719.
=============================================================

Reloaded this page http://rogers2.enclavegames.com/tv/ while debugging its <img> loading issues. No gamepad is connected, but the browser hard crashed to desktop on the given callstack.

Comment 1

11 months ago
Michael, any thoughts?
Component: DOM → DOM: Device Interfaces
Flags: needinfo?(cleu)
I've seen this crash stack several months before which is reported by Jukka as well, but I cannot reproduce it.

It crashes in CFRunLoopStop which is macOS' system API, I suspect there is potential racing condition under the hood since the frame0 is about mutex.

I have tried this website as well but no luck reproducing it yet.

Hi Jukka, what is the model of your Mac?

I think this crash is not related to macOS' version since we have encountered several months ago.
Flags: needinfo?(cleu) → needinfo?(jujjyl)
(Reporter)

Comment 3

11 months ago
My MacBook is 

MacBook Pro (13-inch, 2016, Four Thunderbolt 3 Ports)
3.3 GHz Intel Core i7
16 GB 2133 MHz LPDDR3
Intel Iris Graphics 550 1536 MB
macOS Sierra 10.12.5 (16F73)
Flags: needinfo?(jujjyl)
Very low volume and suspected crash in OS code (I'm guessing we can't influence how we're entering this codepath?) => P3.
Priority: -- → P3
Apple's dev document says that CFRunLoopStop is "generally" thread-safe which is not a good oath.

I will find if there is any other more thread-safe way for it.
You need to log in before you can comment on or make changes to this bug.