[Bug] Infuse crashes on every playback on MacBookPro11,2 (Intel HD 5000) — macOS 15.7.4

Infuse crashes approximately 3–5 seconds after starting any local video file. The app never successfully plays a single frame.

Environment

  • Infuse: 8.3.9 (8.3.5560)

  • macOS: 15.7.4 (24G517)

  • Hardware: MacBook Pro (MacBookPro11,2) — Intel Iris Pro 5200 (HD 5000 series)

  • GPU driver: AppleIntelHD5000GraphicsMTLDriver 18.8.4

Crash details

Faulting thread: CVDisplayLink / com.firecore.renderer.do

Exception: EXC_BAD_ACCESS (SIGSEGV)KERN_INVALID_ADDRESS at 0x0000000000003210

Top of crash stack:

AppleIntelHD5000GraphicsMTLDriver
  IGAccelRenderCommandEncoder::setPipelineState(MTLIGRenderPipelineState*) + 27

The crash occurs when Infuse’s renderer calls setPipelineState() on the Intel Metal driver with what appears to be a null or invalid MTLRenderPipelineState object (address 0x3210 is near-zero, suggesting the pipeline object was never successfully created).

Reproducibility

100% reproducible. Every playback attempt crashes within seconds, regardless of video file format or codec.

Attempted workarounds

Tried setting defaults write com.firecore.infuse hardwareDecoding -bool false — no effect. The crash persists, suggesting the Metal renderer path cannot be disabled via user defaults.

Request

Please add a null-check before passing the pipeline state to the GPU driver, or provide a fallback rendering path for Intel HD 5000 hardware. This GPU’s Metal driver appears to fail silently when creating certain pipeline state objects under macOS 15.

Can you try updating to Infuse 8.4 and macOS 15.7.5 and let us know if this issue persists for you?

Hi James, updated to Infuse 8.4 (8.4.5582) and macOS 15.7.5 (24G624), but the crash still occurs. The crash report looks identical to the previous ones — same faulting thread (CVDisplayLink), same function (IGAccelRenderCommandEncoder::setPipelineState), same invalid address (0x3210). Happy to share the full crash report if it would help.

Yes, if you can send in a report from Infuse on your device and share the crash log that would be helpful. Feel free to send me a PM with the diagnostic code from Infuse and the crash log.