Search Issue Tracker
Active
Under Consideration for 2022.2.X, 2023.1.X
Votes
8
Found in
2022.2.0a18
2023.1.0a1
Issue ID
UUM-7459
Regression
Yes
Crash on mono_class_inflate_generic_type_with_mempool when reloading domain while Unity Jobs package is installed
How to reproduce:
1. Open the attached project (“IN-7238.zip)
2. Click the right mouse button on Assets
3. Click “Create/Assembly Definition”
Expected results: Editor doesn’t crash
Actual results: Editor crashes
Reproducible with: 0.51.0-preview.32 (2022.2.0a10, 2022.2.0a18, 2023.1.0a1)
Not reproducible with: 0.51.0-preview.32 (2022.1.8f1, 2022.2.0a9)
First lines of stacktrace:
{noformat}0x00007ffbae347399 (mono-2.0-bdwgc) [class.c:975] mono_class_inflate_generic_type_with_mempool
0x00007ffbae60a51c (mono-2.0-bdwgc) [mini-generic-sharing.c:726] inflate_info
0x00007ffbae611f67 (mono-2.0-bdwgc) [mini-generic-sharing.c:2830] lookup_or_register_info
0x00007ffbae615101 (mono-2.0-bdwgc) [mini-generic-sharing.c:4305] mini_get_rgctx_entry_slot
0x00007ffbae50c49a (mono-2.0-bdwgc) [mini-runtime.c:1650] mono_resolve_patch_target
0x00007ffbae502ed9 (mono-2.0-bdwgc) [mini.c:2321] mono_codegen {noformat}
Comments (2)
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
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
eusebium
Apr 20, 2023 11:55
Still happens even with the latest com.unity.jobs. The only workaround is to remove that package.
kevinmv
Aug 02, 2022 15:57
Can you try updating to com.unity.collections-1.4.0? This package includes all the com.unity.jobs code and should resolve the issue which was due to circular references between com.unity.jobs and com.unity.collections exposed in 2022.2.
For existing com.unity.jobs users who do not use com.unity.collections, there is a new package com.unity.jobs-0.70.0-preview.7 which will pull in the dependency on collections automatically. Going forward com.unity.jobs has been superseded by com.unity.collections-1.4.0+.