'Segmentation fault: 11' error after upgrading to the latest macOS version

Question

snehdev OP

Created Sep ’24

Replies 5

Boosts 0

Participants 2

Today I updated my macbook pro to macOS sequoia. with this I also downloaded the latest Xcode and visionOS 2 packages.

I had a working project. Which did work with my vision pro which is updated to the latest visionOS 2. But now whenever I try to click on preview in xcode while editing a swift file I am receiving the following error:

(lot of lines here)

Library/Developer/Xcode/DerivedData/test2-fznbrpphddkqdaddrzamkayoajjm/Build/Intermediates.noindex/RealityKitContent.build/Debug-xrsimulator/RealityKitContent_RealityKitContent.build/DerivedSources/RealityAssetsGenerated/CustomComponentUSDInitializers.usda error: Tool terminated by signal 'Segmentation fault: 11'

I tried exiting and restarting my mac but the problem is not going away. Can someone help me with this?

Thank you!

Answered by Vision Pro Engineer in 807328022

Hi @snehdev

The error is related to CustomComponentUSDInitializers.usda in your Reality Composer Pro project. One way to find the culprit is to remove entities and/or their components until you find the offending item/items. I vaguely recall seeing something like this when someone made a change to a component that was not backward compatible. That is, someone added a required field to a component used by an existing Reality Composer Pro project.

That said, it sounds like your macOS, visionOS and Xcode are all up to date, but you get a seg fault. Do you get this error with newly created projects? Either way this seems like a bug. Please file a bug report with the information you provided here. If the bug is limited to your project please include your project.

Bug Reporting: How and Why? has tips on creating your bug report.

Boost

Answer 1

Vision Pro Engineer OP

Apple

Oct ’24

Accepted Answer

Hi @snehdev

The error is related to CustomComponentUSDInitializers.usda in your Reality Composer Pro project. One way to find the culprit is to remove entities and/or their components until you find the offending item/items. I vaguely recall seeing something like this when someone made a change to a component that was not backward compatible. That is, someone added a required field to a component used by an existing Reality Composer Pro project.

That said, it sounds like your macOS, visionOS and Xcode are all up to date, but you get a seg fault. Do you get this error with newly created projects? Either way this seems like a bug. Please file a bug report with the information you provided here. If the bug is limited to your project please include your project.

Bug Reporting: How and Why? has tips on creating your bug report.

1

Answer 2

snehdev OP

Oct ’24

Hi, I have filed a bug report. I will look into my reality composer pro entities and components.

I created this project for visionOS 1.2 and it worked on that version.

Thanks for the inputs!

0

Answer 3

snehdev OP

Oct ’24

I found something new on this. If I remove the usdc files from my project and keep everything else I don't get the segmentation fault: 11 error. Does visionOS 2 not support usdc files? @Vision Pro Engineer

0

Answer 4

Vision Pro Engineer OP

Apple

Oct ’24

Hi @snehdev

visionOS does support usdc, but I've seen cases where certain usd* files (for reasons I'm unaware of) cause Reality Kit to throw errors. See Creating USD files for Apple devices guidance on creating assets. Nonetheless a segfault is unexpected. Thanks for filing the bug report.

In the meantime, I suggest you try to convert your usdc file to usdz using Reality Converter. I'm not sure if it will fix the issue, but it's worth trying.

Please let me know how it turns out.

1

Answer 5

snehdev OP

1h

Hi @Vision Pro Engineer Converting to USDZ does work. I have multiple models and it will be a lot of work.

I didn't receive any feedback on the bug report I filled up. I wanted to ask should I proceed with converting all my models or wait for the feedback. How long does it usually take to receive a feedback?

Thanks!

0