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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
fogsight
Mar 31, 2016 00:49
Encountered this error after introducing Vector3.SmoothDamp to center main camera on UI objects calling a Coroutine with dozen of cycles and 0.1 second loop delay.
Error pops-up seemingly random just during this activity, have not had any crashes yet.
5.3.4f1
screenname_taken
Mar 11, 2016 13:49
I also have the same issue. 5.3.3p2.
Tried clicking the error to see what is causing it, but the editor points at nowhere.
Snorkel
Mar 10, 2016 17:18
I have the same issue. Crash after random number of
"m_size < k_reference_bit" messages
In 5.3.3p1