Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
2
Found in
2020.1.0a7
2020.1.0b4
Issue ID
1235202
Regression
Yes
Player crash when calling ReadInt32 from BinaryReader several hundred thousand times
How to reproduce:
1. Open the attached project (1235202.zip)
2. Open the Main scene from the Project window
3. Open the "Build Settings" window (File > Build Settings...)
4. In the "Build Settings" enable "Development Build" and build the project
5. Run the build's executable
6. After the splash screen press the M key
7. If the player doesn't crash and is frozen for more than 10 seconds press the mouse on the player window a couple times until another window opens up that the program is not responding. Close the program and repeat steps 5, 6 and 7.
Reproducible with: 2020.1.0a7, 2020.1.0b10, 2020.2.0a12
Not reproducible with 2019.3.14f1, 2020.1.0a6
Notes:
1. Tested on Windows 10 and Ubuntu 18.04
2. On Ubuntu reproduces very rarely
3. Often takes more than 10 tries to reproduce, on Windows 10 after the first crash the build should crash every time
-
halfvoxel
May 22, 2020 11:09
Discussion related to this bug: https://forum.arongranberg.com/t/large-recasts-standalone-crash/8271/3
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a15
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b14