Search Issue Tracker
Fixed in 1.5/2.0
Votes
1
Found in [Package]
2019.3
2020.2
2020.2.0a7
Issue ID
1237679
Regression
No
Crash on mono_object_get_class when entering Play mode after removing Burst without rebuilding Asset Bundle
How to reproduce:
1. Open the project "1237679"
2. Remove the Burst package from the project
3. Enter Play mode in the SampleScene
4. Observe the crash
Reproducible with: 2019.3.10f1, 2020.1.0b5, 2020.2.0a7
Could not test with: 2017.4.39f1 (no Burst package), 2018.4.31f1 (Console errors regarding AnimationStream)
Note:
1. To reproduce it multiple times, install and uninstall the Burst package, then enter Play mode
2. The crash does not occur if the Asset Bundle is rebuilt (Tools > Build AssetBundle)
First 5 lines of the stack trace:
#0 0x0000014591877a in mono_object_get_class
#1 0x0000010835153e in scripting_object_get_class(ScriptingObjectPtr)
#2 0x000001073afa57 in BurstCompilerService::CompileAsync(ScriptingClassPtr, ScriptingObjectPtr, void*, int, void (*)(void*, int, void*), void (*)(void*, BurstLogType, char const*, char const*, int))
#3 0x00000107a51934 in CreateJobReflectionData(ScriptingSystemTypeObjectPtr, ScriptingSystemTypeObjectPtr, JobType, ScriptingObjectPtr*, core::basic_string<char, core::StringStorageDefault<char> >&)
#4 0x00000107a53b6d in CreateJobReflectionData(ScriptingSystemTypeObjectPtr, ScriptingSystemTypeObjectPtr, JobType, ScriptingObjectPtr, ScriptingObjectPtr, ScriptingObjectPtr)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
- [VFX] Creating a long Group Node name breaks nodes boarders
Add comment