Search Issue Tracker
Fixed
Fixed in 1.3.X - Entities, 7000.0.0a1
Votes
1
Found in [Package]
1.0.16 (Patch 4)
1.2.0-exp.3 - Entities
1.3.X - Entities
7000.0.0a1
Issue ID
ECSB-781
Regression
No
Crash on Player exit when UNITY_DISABLE_AUTOMATIC_SYSTEM_BOOTSTRAP is enabled
How to reproduce:
1. Open the attached project "PPT.zip"
2. Build And Run the project
3. Exit the Player
Reproducible with: 2022.3.14f1 (1.0.16, 1.2.0-exp.3)
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
First lines of stack trace:
0x00007FF93CDCDB55 (UnityPlayer) (function-name not available)
0x00007FF9D5CBE858 (USER32) CallWindowProcW
0x00007FF9D5CBE299 (USER32) DispatchMessageW
0x00007FF93CFCD858 (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF93CDCF149)
0x00007FF93CDCF149 (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF93CDD250B)
0x00007FF93CDD250B (UnityPlayer) (function-name not available)
0x00007FF93CDD27AB (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF67D0911F2)
0x00007FF67D0911F2 (PPT) (function-name not available)
0x00007FF9D6637344 (KERNEL32) BaseThreadInitThunk
0x00007FF9D77826B1 (ntdll) RtlUserThreadStart
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
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
Resolution Note (fix version 1.3.X - Entities):
This was fixed in 1.2.3 - not sure why a 1.3.X port was opened for it. The fix was in 1.3.X