Search Issue Tracker
Active
Votes
0
Found in
6000.0.60f1
6000.2.8f1
6000.3.0b6
6000.4.0a2
Issue ID
UUM-122598
Regression
No
Crash with multiple stack traces when performing various actions with the Cesium package installed
A crash in the Unity Editor has been observed, affecting various workflows. These crashes happen when:
- Opening the attached “IN-112305” project
- Entering or exiting Play mode in the SampleScene
- Closing the project
- Upgrading the Cesium package
- Removing the Cesium package
Reproducible with: 2023.2.0a17, 6000.0.60f1, 6000.2.8f1, 6000.3.0b6, 6000.4.0a2
Couldn’t test with: 2023.2.0a16 (could not solve package errors from downgrading)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- Reproduction is inconsistent but happens most consistently when entering Play mode and exiting the project
- The stack traces are different depending on how the crash happened and which version it crashed on
First few lines of the stack trace:
Entering or exiting play mode:
0x00007FFAC0767573 (Unity) Object::SetCachedScriptingObject
0x00007FFAC0B06242 (Unity) CommitBatchDelete
0x00007FFAC0AFAB69 (Unity) DestroyObjectHighLevel_Internal
0x00007FFAC0AFA944 (Unity) DestroyObjectHighLevel
0x00007FFAC009F656 (Unity) Object_CUSTOM_DestroyImmediate
Closing the project:
0x00007FFA964F7573 (Unity) Object::SetCachedScriptingObject
0x00007FFA96896242 (Unity) CommitBatchDelete
0x00007FFA9688A85A (Unity) DestroyGameObjectRecursive
0x00007FFA9688A6DF (Unity) DestroyGameObjectRecursive
0x00007FFA9688A6DF (Unity) DestroyGameObjectRecursive
Upgrading the Cesium package:
0x00007FFAA2D91314 (Unity) Transfer_UnityEngineObject<StreamedBinaryWrite,0>
0x00007FFAA2CDCB9C (Unity) ExecuteSerializationCommands<JSONRead>
0x00007FFAA2CF9838 (Unity) <lambda_23502d5cf47c99f01792cd87488ce116>::operator()
0x00007FFAA2CF40E6 (Unity) TransferScriptingObject<StreamedBinaryWrite>
0x00007FFAA2CFF439 (Unity) SerializableManagedRefBackupGenerator::ExtractBackupFromInstance
Deleting the Cesium package:
0x00007FFAF7F1010F (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\memory-manager.c:156] mono_mem_manager_alloc0
0x00007FFAF8120CD5 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\mini-generic-sharing.c:3081] mono_class_fill_runtime_generic_context
0x00007FFAF810FFD7 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\mini-trampolines.c:1031] mono_rgctx_lazy_fetch_trampoline
0x000001DCB7A008C6 ((<unknown>)) (function-name not available)
0x000001DD70A10763 (Mono JIT Code) System.Collections.Generic.List`1<T_REF>:GetEnumerator ()
Opening the project:
0x00007FFC78329E74 (Unity) scripting_method_invoke
0x00007FFC78301C53 (Unity) ScriptingInvocation::Invoke
0x00007FFC78301D3E (Unity) ScriptingInvocation::InvokeChecked
0x00007FFC783AD0C6 (Unity) SerializableManagedRef::CallMethod
0x00007FFC782FCA84 (Unity) MonoBehaviour::WillUnloadScriptableObject
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Pressing “-” twice to remove a Tag in Project Settings > Tags and Layers throws errors in the Console window
- "State comes from an incompatible keyword space" error when clicking on a shader
- Test Runner's Player test fails when the IL2CPP scripting backend is selected
- Not all of the Profiler Modules can be reordered
- [Accelerator] Texture uploads to the cache server are duplicated when switching between Texture Formats
Add comment