Search Issue Tracker
Fixed in 5.3.6
Votes
31
Found in
5.3.3p1
Issue ID
774423
Regression
Yes
[UI?] After multiple m_size < k_reference_bit errors Unity crashes at FullParameterPreparer::OnPrepareTexture
Steps to reproduce:
1. Open attached project "774423.zip"
2. Open scene "Assets/Scenes/GameScene"
3. Run it
4. Press TAB twice
5. Notice "m_size < k_reference_bit" errors start to accumulate and then Unity crashes
Note: Sometimes Unity crashes right away, other times it takes more than 50 errors to be printed before crash.
Not reproducible: 5.3.3f1
Regression introduced in: 5.3.3p1
Reproduced with: 5.3.3p3, 5.4.0b10
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
- [iOS] No fallback for Light Probe Proxy Volume for devices which do not support 32bit floating point textures
- Layout is not valid unless the GameView is resized
- [iOS] Directional lightmap compression causes lightmap artifacts
- NullReferenceExceptions in PreprocessReflectionProbeData
- [2d][Sprite Import] Specific Sprite seems to be cutoff when added into the scene
Rickshao
Jul 27, 2016 09:29
Occurs in Unity 5.3.5f1
hawken
Jun 11, 2016 06:19
I'm seeing this issue in 5.3.5
m_size < k_reference_bit
ph0b0s
Jun 03, 2016 14:54
Waiting for 5.3.6, hit this problem in the 5.3.5f1.
ResoDev
May 24, 2016 18:38
Just crashed because of this error in 5.3.4. I wasn't doing anything fancy, just displaying text and images in UI. I'm going to update to 5.3.5 and hope that this issue will be resolved, although it's written "resolved in 5.3.6" which is not out yet.
Nodrap
May 24, 2016 16:31
Hit the problem too. Am rendering a canvas to a texture and the screen flickers a few times and then the error log starts to show the "m_size..." and it will crash after 10-30 seconds. 5.3.4
Naphier
Apr 29, 2016 21:58
Bummer, now I'm getting consistent crashes. Seems to happen when moving or scaling UI components that are being rendered to texture. Now we can't animate out UI onto a texture.
Naphier
Apr 29, 2016 19:08
5.3.4f1 no crash, but this message occurs when we're doing some scaling animations on some uGUI images that are rendered to texture.
MisterJones
Apr 23, 2016 00:25
Still occurs in 5.3.4p4
fredlllll
Apr 05, 2016 12:45
also have the problem since 5.3.4
we also draw the gui on a rendertarget. but the error usually pops up when something with animations is happening. when i start the game i can run around for 5 seconds and then the editor crashes
Silent8Strike
Mar 31, 2016 02:36
Same issue in 5.3.4f1, caused by rendering a uGUI canvas to a render texture. If I disable the camera rendering the GUI the errors no longer occur.
If I leave the camera enabled the errors continue until the editor inevitably crashes.