Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0b3
Issue ID
906111
Regression
No
Collab and debugallocator do not work together on 2017.1
Collab and debugallocator do not work together on 2017.1
1. What happened
On both staging and prod, 2017.1 crashes when attempting to use collab after you've started Unity with command line -debug allocator argument. An error is thrown to my console on crash, "Segmentation fault". See screenshot.
2. How we can reproduce it using the example you attached
1. Start Unity with argument -debugallocator
2. DL some content from the asset store (I used the Sebastian model from the Adam series)
3. In the services window, enable collab and attempt to sync
4. Observe crash.
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
- [VisionOS] visionos build do not add plugin or frameworks
- Mathf.Floor produces inconsistent results when processing Physics.Raycast.Point X coordinate
- Crash on CheckGameObjectsAndAddMissingRequiredComponents when opening a specific project
- Batch Mode and Cloud Build get stuck at 'Scanning for ADB Devices' when building for the Android or iOS platforms
- HDRP LightLateUpdate allocates every frame for each light in the scene when in Play Mode
This is a duplicate of issue #906797