Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.1.0a4
Issue ID
682282
Regression
No
[NativePlugin] Crash in native plugin does not generate crash stack trace in log and no crash dump files
To reproduce:
Step 1) Open the attached unity project, and then the scene.unity
Step 2) Select File/Build Settings... and confirm: Windows, x86_64, Development Build, Script Debugging
Step 3) Build, and run the standalone build
Step 4) press the space bar to crash in the native plug-in (RenderingPlugin.dll)
Step 5) observe that no dialog appears reporting that crash dump files were saved, and no crash dump files were saved in the standalone build directory
Step 6) open output_log.txt in the _Data folder where you built the standalone player, and observe that the stack trace is empty at the end of the file
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment