Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0p1
Issue ID
1004179
Regression
No
Selection.objects = null causes TLS Allocator errors in Play Mode
How to reproduce:
1. Download and open the attached project file
2. Attach the script to an object.
3. Select an Object and press second button (The first button in its inspector clears the selection as expected. The second button does too, but throws a NullReferenceException in Play Mode and causes the following message and error to show up repeatedly until I restart the editor)
Actual result: Unity throws a NullReferenceException in Play Mode and causes the following message and error to show up repeatedly until Editor is restarted:
Message:
Allocation of 40 bytes at 0000000007B49060
Error:
Assertion failed: TLS Allocator ALLOC_TEMP_THREAD, underlying allocator ALLOC_TEMP_THREAD has unfreed allocations, size 40
Reproduced with: 2017.1.3p1, 2017.2.2f1, 2017.3.1p2, 2018.1.0b8, 2018.2.0a1
Note: On 2018.2.0a1 there is no more error, only Message appears
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
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.