Search Issue Tracker

Active

Votes

0

Found in

6000.0.57f1

6000.2.4f1

6000.3.0b1

Issue ID

UUM-116758

Regression

Yes

Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"

-

How to reproduce:
1. Extract the “lights-memory-tests.zip“ project
2. Install Python on the computer (the reporter specified Python 3.13)
3. Open the Command Prompt as an administrator
4. Install two extensions by running “py -m pip install pillow pywin32“ command, in the Command Prompt window
5. Within the project directory, open the “project_config.json” file and change the “unity_version“ and “unity_exe“ values to the version to be tested
6. Save the changes
7. Run “[full path to the project]\run_project.bat -t build,split” command, in the Command Prompt window
7. Wait until the build and tests finish (might take 10+ minutes)
8. Observe the Yellow text in the Command Prompt window

Expected result: The memory difference is insignificant (usually <10MB)
Actual result: The memory difference is significant (>20MB), which indicates a memory leak

Reproducible in: 6000.0.52f1, 6000.0.57f1, 6000.2.4f1, 6000.3.0b1
Not reproducible in: 6000.0.51f1 (a206c6c19c75)

Reproduced on: Windows 11
Not reproduced on: No other environment tested

Reproducible with GPU: NVIDIA GeForce RTX 3080 Ti
Not reproducible with GPU: NVIDIA RTX 3500 Ada

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.