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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
This is a duplicate of issue #906797