Search Issue Tracker
By Design
Votes
0
Found in
2022.3.10f1
2023.1.14f1
2023.2.0b10
2023.3.0a7
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-52884
Regression
No
TLS Allocator ALLOC_TEMP_TLS error is thrown In the Play Mode when using LazySingleton
How to reproduce:
1. Open the user-attached project “com.lupos.kiss”
2. Open the “TitleScene” scene
3. Enter the Play Mode
4. Observe the Console
Expected result: There are no errors thrown in the Console
Actual result: The “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 528” error is thrown into the Console
Reproducible with: 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a7
Couldn’t test with: 2021.3.30f1 (The project is broken after the downgrade)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
The TLS allocator runs out of (stack) memory due to infinite recursion caused by Kiss.Runtime.Components.Singleton.LazySingletonMb Awake() (Assets/com.lupos.kiss/Runtime/Components/Singleton/LazySingletonMb.cs:32). There is no good way of detecting infinite recursion invokation from the native code side from user scripts. Please look through the code path from the script side to determine the recursion root cause.