Search Issue Tracker
Active
Under Consideration for 2022.3.X
Votes
5
Found in
2022.3.12f1
2023.1.19f1
2023.2.0b16
2023.3.0a12
Issue ID
UUM-55046
Regression
Yes
Allocation errors are logged to the Console when creating a new project and the “Connect to Unity Cloud” option is enabled
How to reproduce:
1. Open the Hub
2. Make sure the “Connect to Unity Cloud” option is enabled
3. Create a new project with any template
4. Observe the Console
Expected result: No warnings or errors regarding allocations are logged to the Console
Actual result: Allocation warnings and errors are logged to the Console
Reproduced with: 2022.2.0a14, 2022.3.12f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a12
Not reproduced with: 2021.3.32f1, 2022.2.0a13
Reproduced on: macOS 14.0 (by reporter), Windows 11
Not reproducible on: No other environment tested
Notes:
1. It might take at least 2 attempts to reproduce
2. In non-reproducible versions “[Collab] Collab service is deprecated and has been replaced with PlasticSCM” error is logged to the Console
3. Tested with “3D (Core)”, “3D (URP)”, “3D (HDRP)”, “2D (Core)”, “2D (URP)”, and “VR” templates
4. Not reproducible after opening the project again
Messages logged to the Console:
1. Allocation of 37 bytes at 0000016EA0900410
2. TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 37
3. Internal: Stack allocator ALLOC_TEMP_MAIN has unfreed allocations, size 37
4. To Debug, run app with -diag-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
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
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
- "Untracked" memory is logged by the Profiler when small allocations for delegates and big allocations for new array creations happen simultaneously
- Rotation value change on the X-axis gets stuck when using transform.rotation.eulerAngles
- The Editor process is not being put in front when focused after using an un-docked feature window
- Motion Vectors for an object are included in the URP Motion Vector pass when the object's layer mask is filtered out
Shaelle
Apr 30, 2024 22:51
I think I've got the same error today with 2023.2.6
Console output:
"
...\EnsureThat.Reflection.cs(20,12): error CS1519: Invalid token '
Allocation of 37 bytes at 0000013B20300390
37 39 65 61 30 37 31 65 2d 32 32 30 62 2d 34 35 79ea071e-220b-45
39 66 2d 62 36 61 37 2d 62 62 36 66 64 34 62 32 9f-b6a7-bb6fd4b2
32 65 34 62 00 .. .. .. .. .. .. .. .. .. .. .. 2e4b.
TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 37
Internal: Stack allocator ALLOC_TEMP_MAIN has unfreed allocations, size 37
"
Most likely connected to the Visual Scripting package: after I removed it from the project, errors dissapeared.
Alfux
Apr 25, 2024 08:39
Just got the same issue in version 2023.2.14f1, on macOS Sonoma 14.4.1 with a newly created 3D(Core) project:
[10:28:16] Allocation of 37 bytes at 0x15480390
[10:28:16] 63 38 38 34 36 63 31 61 2d 36 38 34 62 2d 34 35 8846c1a-684b-45
[10:28:16] 31 32 2d 62 33 38 62 2d 31 32 64 35 39 63 31 63 12-b38b-12d59c1c
[10:28:16] 63 34 32 30 00 ..
C420
[10:28:16] TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 37
[10:28:16] Internal: Stack allocator ALLOC_TEMP_MAIN has unfreed allocations, size 37
[10:28:16] To Debug, run app with -diag-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
lexajan
Jan 28, 2024 01:29
To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.