Closed Bug 1709026 Opened 3 years ago Closed 7 months ago

Crash in [@ __pthread_kill | abort | USC::CreateCompiler], likely Hackintosh related

Categories

(Core :: Graphics: WebRender, defect)

Unspecified
macOS
defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: gsvelto, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/69b921d1-4b02-4cf6-9ca2-3dc5c0210501

Reason: EXC_SOFTWARE / SIGABRT

Top 10 frames of crashing thread:

0 libsystem_kernel.dylib __pthread_kill 
1 libsystem_c.dylib abort 
2 libsystem_c.dylib __assert_rtn 
3 AppleIntelKBLGraphicsGLDriver USC::CreateCompiler 
4 AppleIntelKBLGraphicsGLDriver USC::CreateCompiler 
5 AppleIntelKBLGraphicsGLDriver GenContext::Initialize 
6 AppleIntelKBLGraphicsGLDriver glrInitializeContext 
7 libGPUSupportMercury.dylib gldCreateContext 
8 GLEngine gliCreateContextWithShared 
9 OpenGL CGLCreateContext 

This is a macOS-specific crash happening deep within Apple's driver code. Non-nightly versions of Firefox are affected so it doesn't appear to be a regression on our end (though it could be an old bug). It might also be a regression on Apple's side.

Blocks: wr-mac
Severity: -- → S3

For what it's worth, a potentially interesting mac_crash_info section showed up in a recent crash report with this signature:

bp-d5062df2-9cf9-421f-9d71-1be0f0210713

    {
      "num_records": 1,
      "records": [
        {
          "message": "Assertion failed: (0), function CreateCompiler, file /Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-14.7.8/GLRenderer/kbl/usc_interface.cpp, line 1676.\n",
          "module": "/usr/lib/system/libsystem_c.dylib"
        }
      ]
    }
Crash Signature: [@ __pthread_kill | abort | USC::CreateCompiler] → [@ __pthread_kill | abort | USC::CreateCompiler] [@ __pthread_kill | pthread_kill | abort | USC::CreateCompiler ]

After googling, https://github.com/alacritty/alacritty/issues/4375 seems to indicate this might be a problem with so-called "hackintosh" setups not recognizing the display hardware, and it seems like the user must properly configure their system to avoid it.

Interesting. There are quite a few hits for "usc_interface.cpp, line 1676", which is the last part of the "message" from the mac crash info from comment #1. These include the one you mentioned. All of those I looked at have to do with Hackintoshes.

Summary: Crash in [@ __pthread_kill | abort | USC::CreateCompiler] → Crash in [@ __pthread_kill | abort | USC::CreateCompiler], possibly Hackintosh related

I haven't noticed many Mozilla bugs associated with weird hardware or settings. But there's at least one other proven one -- bug 1722827. And there may be more.

See Also: → 1722827
Summary: Crash in [@ __pthread_kill | abort | USC::CreateCompiler], possibly Hackintosh related → Crash in [@ __pthread_kill | abort | USC::CreateCompiler], likely Hackintosh related

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME

These are still happening.

Crash Signature: [@ __pthread_kill | abort | USC::CreateCompiler] [@ __pthread_kill | pthread_kill | abort | USC::CreateCompiler ] → [@ __pthread_kill | abort | USC::CreateCompiler] [@ __pthread_kill | pthread_kill | abort | USC::CreateCompiler ] [@ pthread_kill | abort | USC::CreateCompiler ]
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

Given the volume and lack of repro steps, there is nothing we can do about this. Closing for now, but please reopen if volume or relevant information changes.

Status: REOPENED → RESOLVED
Closed: 2 years ago7 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.