Search Issue Tracker
Third Party Issue
Third Party Issue in 6000.4.X
Votes
0
Found in [Package]
6000.0.63f1
6000.2.15f1
6000.3.0f1
6000.4.0a5
Issue ID
MOXRB-188
Regression
Yes
Crash on folly::detail::safe_assert_terminate_v when updating the Meta XR SDK Packages
Steps to reproduce:
1. Open the “user’s attached project”
2. Open “Windows/Package Manager”
3. Find the “Meta XR All-in-One SDK“ Package
3. Go to the Version History tab and update the Package (consistent crash with 81.0.0 and 78.0.0 versions)
4. Observe the crash
Reproducible with versions: 6000.0.35f1, 6000.0.63f1, 6000.2.15f1, 6000.3.0f1, 6000.4.0a5
Not reproducible with versions: 6000.0.34f1, 6000.5.0a2
Reproducible on: macOS 15.7.1 (M1 Max)
Not reproducible on: Windows 11
First few lines of StackTraces:
#0 0x0000019b23a388 in __pthread_kill
#1 0x0000019b17c9e4 in abort
#2 0x0000040d3b9ca0 in folly::detail::(anonymous namespace)::safe_assert_terminate_v(folly::detail::safe_assert_arg const, int, char)
#3 0x0000040d3b9bd8 in folly::detail::(anonymous namespace)::safe_assert_terminate_v(folly::detail::safe_assert_arg const, int, char)
#4 0x0000040d68643c in folly::detail::singletonWarnDoubleRegistrationAndAbort(folly::detail::TypeDescriptor const&)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
Resolution Note:
Our evaluation of this issue points to the crash occurring in the Meta All-in-one SDK package code. We have shared this issue with our partners at Meta and will be resolving this as a "Third Party Issue".
Resolution Note (6000.4.X):
Our evaluation of this issue points to the crash occurring in the Meta All-in-one SDK package code. We have shared this issue with our partners at Meta and will be resolving this as a "Third Party Issue".