Search Issue Tracker
Won't Fix
Unknown (hidden) 2019.4.X, 2020.3.X, 2021.3.X, 2022.1.X, 2022.2.X
Votes
0
Found in
2019.4.38f1
2020.3.34f1
2021.3.1f1
2022.1.0b16
2022.2.0a15
Issue ID
UUM-6032
Regression
No
Unity crashes when entering Play Mode using DLL files
How to reproduce:
1. Open the attached project "1428243_DLL Test"
2. Enter Play Mode
Expected result: Play Mode is entered
Actual result: Unity Editor crashes
Reproduced in: 2019.4.38f1, 2020.3.34f1, 2021.3.1f1, 2022.1.0b16, 2022.2.0a15
Stack trace:
0x00007ffa55e7276b (Procedural Generation Library) HelloWorld
0x00007ffa55e71aee (Procedural Generation Library) HelloWorld
0x00007ffa55e72874 (Procedural Generation Library) HelloWorld
0x00007ffa55e74342 (Procedural Generation Library) HelloWorld
0x0000020b849cfa87 (Mono JIT Code) (wrapper managed-to-native) GameManager:HelloWorld ()
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Unity is not able to recover from this exception.
The user code provided calls native code via PInvoke. The native code causes an access violation and Unity is not able to reliably recover from this .
If you believe that the access violation is caused by Unity engine code, please respond to reopen the bug with additional details.