Search Issue Tracker
Active
Votes
0
Found in
2022.3.60f1
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "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
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment