Search Issue Tracker
Fixed in 2019.4.X
Votes
1
Found in
2018.4
2019.4
2019.4.6f1
Issue ID
1267258
Regression
No
Crash when calling new Texture2D(16384, 16384, TextureFormat.RGBAFloat, false, false)
How to reproduce:
1. Open attached project "Case_1267258"
2. In the Menu Bar click Test -> Crashtest
3. If the crash does not occur, repeat step 2
Reproducible with: 2018.4.26f1, 2019.4.9f1
First lines of the stack trace (2020.1.0a8 and up, OpenGLCore, OpenGLES3):
0x00007FF6D5AEF0D7 (Unity) DynamicHeapAllocator::Allocate
0x00007FF6D5AE405A (Unity) DualThreadAllocator<DynamicHeapAllocator>::Allocate
0x00007FF6D5ACB1A6 (Unity) MemoryManager::Allocate
0x00007FF6D5AE0A1C (Unity) malloc_internal
0x00007FF6D658BECF (Unity) dynamic_array_detail::dynamic_array_data::resize_buffer
0x00007FF6D51EF6F8 (Unity) dynamic_array<signed char,0>::resize_buffer_nocheck
0x00007FF6D5F97E12 (Unity) SharedTextureData::SharedTextureData
0x00007FF6D5ED8A3A (Unity) Texture2D::InitTextureInternal
First lines of the stack trace (below 2020.1.0a8, OpenGLCore, OpenGLES3):
0x00007FFAAE4C2C8D (nvoglv64) DrvPresentBuffers
0x00007FFAAE3D155B (nvoglv64) DrvPresentBuffers
0x00007FFAAE3D0B29 (nvoglv64) DrvPresentBuffers
0x00007FFAAE3D0EAF (nvoglv64) DrvPresentBuffers
Notes:
1. Reproduces with OpenGLCore, OpenGLES3
2. Stack trace changes from 2020.1.0a8 when using OpenGLCore and OpenGLES3
3. Direct3D11 throws errors regarding failure to create Texture but does not crash
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.18f1