Repeated SIGABRT in RenderBox Metal device init (`RB::load_library`)

[sammarcus]

Describe the bug

Contextify aborts with SIGABRT on the com.apple.RenderBox.Device queue while SwiftUI's RenderBox loads its Metal shader library. Six crash reports with an identical stack over five days, plus two related variants.

0  libsystem_kernel.dylib  __pthread_kill
1  libsystem_pthread.dylib pthread_kill
2  libsystem_c.dylib       abort
3  RenderBox               RB::precondition_failure(char const*, ...)
4  RenderBox               RB::(anonymous namespace)::load_library(NSBundle*, id<MTLDevice>) (.cold.2)
5  RenderBox               RB::(anonymous namespace)::load_library(NSBundle*, id<MTLDevice>)
6  RenderBox               RB::Device::preload_resources()
7  RenderBox               RB::Device::Device(RBDevice*, id<MTLDevice>)::$_7::__invoke(void*)

Two variants: one crash reached the same failure from CoreAnimation (CA::CG::Queue → CA::OGL::new_metal_context assert), triggered by a click in an outline view; one produced an extra uncaught ObjC exception during NSView layout at the same second.

Not a machine-wide GPU problem, no other app on this machine has ever produced this signature, and it reproduces across two separate boot sessions at uptimes from 16 hours to 9.6 days.

To Reproduce

No reliable repro. It fires both in foreground and background, at launch and 40+ minutes in. One instance came from a plain click in an outline view.

Expected behavior

Metal library load failure shouldn't terminate the app.

Environment:

• macOS version: 26.6 (25G72)
• Contextify version: 1.7.7 (42)
• Installation method: App Store
• Hardware: Mac15,10, M3 Max, 96 GB

The precondition_failure message string isn't in the .ips , though.... let me know if you want the crash logs emailed?

[banagale]

Hello Sam,

Thank you very much for the bug report. I have not had this happen yet, so I am curious to find and squash it for you.

I would appreciate those crash logs if you still have them, you can send them to rob@contextify.sh.

If you're open to it, I'd like to issue you a TestFlight of the app that includes proper crash logging.

That should allow me to get a better idea for what is going on and hopefully issue you a follow-up that proves a fix.

Here is a link to sign up for the TestFlight: https://testflight.apple.com/join/Bfx7pAm9

[banagale]

Hey there, I've uploaded the testflight containing the crash logging and it was approved for release.

If you sign up / join the group using the above URL you should have immediate access. Please let me know if you hit any trip ups.

[banagale]

@sammarcus Howdy. I wanted to ping you on this, see if you saw it. I'm converging on a 1.8.0 release that will include the crash logging included on the TestFlight.

I'd love to know if your issue is worked out / if there is something else I can do to assist.