Search Issue Tracker
Duplicate
Votes
1
Found in
2018.3.0b11
Issue ID
1104587
Regression
No
[AMD only] Unity Player crashes on ThreadedBlockAllocatingBuffer::HandleOutOfBufferToReadFrom
How to reproduce:
1. Open the attached project
2. Press Assets > AssetBundles > Build All Asset bundles (including tactics)
3. Build & Run the project
4. Walk around with the characters inside the game
Actual result: Unity crashes.
Reproducible with 2019.1.0a12(5aef5b), 2018.3.0b11.
Not reproducible with: 2019.2.0a4, 2019.2.0a1, 2019.1.0a15, 2019.1.0a12 (5175bc) 2018.3.5f1
Notes:
Can't check on 2018.2 and lower because level_3 prefab causes a crash on import (the bug is reported)
The crash happens randomly: Sometimes on walking, sometimes on seeing enemy, sometimes just while moving the mouse around the grid.
There are many "Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak" thrown before the crash.
The crash and leak are reproducible only with AMD graphic cards.
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
noblegaijin
Jan 02, 2019 15:18
I am having the same issue on my machine. Whenever I move objects in 3D space (even in the editor), the engine crashes.