Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0f2
Issue ID
1130899
Regression
No
Unity Editor silently crashes when calling a function inside a C++ DLL
To reproduce:
1. Download attached project “TestNativedll.zip" and open in Unity
2. Open "SampleScene" scene
3. Enter to Play mode
Expected results: Unity Editor successfully enters to Play mode
Actual results: Unity Editor silently crashes
Notes:
- This issue appears both on Windows and macOS
- Cannot check on Standalone because Build fails with Errors which are shared in Comments section
- User attached the C++ project "Core.zip" which was used to produce the DLL
Reproduced on Unity 2017.4.0f1, 2017.4.20f2, 2018.3.7f1, 2019.1.0b5 and 2019.2.0a6
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Unity does not support the use of managed C++ dlls. Mixed mode assemblies definitely won't work, and even pure C++/CLI assemblies are not tested or expected to work. Access to native code should be done via C APIs and PInvoke.