Search Issue Tracker
Fixed
Fixed in 2022.3.62f1, 6000.0.49f1, 6000.1.2f1, 6000.2.0a10, 7000.0.0a26
Votes
0
Found in
2022.3.60f1
6000.0.1f1
6000.1.0a2
6000.2.0a1
Issue ID
UUM-100968
Regression
Yes
"To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
How to reproduce:
1. Open the “JobTempMemoryLeakValidationTest“ project
2. Open the “SampleScene“
3. Enter Play mode
4. Observe the Console
Expected result: Only details about the memory leak are printed
Actual result: "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed
Reproducible with: 2022.2.0b11 (fbf253239670), 2022.3.60f1, 2023.1.0b1
Not reproducible with: 2022.2.0b10( 23300ef499b2), 6000.0.43f1, 6000.1.0b11, 6000.2.0a7
Fixed in: 2023.1.0b2
Reproducible on: Windows 10, macOS 15.1.1
Not reproducible on: no other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment