Search Issue Tracker
Fixed
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.57f1
6000.2.3f1
6000.3.0a4
Issue ID
UUM-116316
Regression
No
RenderGraph ContextData buffer leaks in IL2CPP when using Native Leak Detection
How to reproduce:
1. Open the attached "IN-113450" project
2. Navigate to “File > Build Profiles”
3. Select the Windows Platform
4. Click on the “Build“ button
5. Wait for the build to complete successfully
6. Open Command Prompt
7. Navigate to the build output folder
8. Run the project by typing: [ProjectName].exe -native-leak-detection EnabledWithStackTrace
9. Wait a couple of minutes while the project runs
10. Exit the built project
11. Open the Player Log (can be accessed through navigating to “Console Window > Three-dot menu > Open Player Log“)
Expected result: No issues in the Player Log
Actual result: “Leak Detected” message appears in the Player Log (at the bottom of the file)
Reproducible with: 6000.0.57f1, 6000.2.3f1, 6000.3.0a4
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: The{color:#ffbdad} {color}Scriptable Render Pipeline Core package has been modified to add logging when ContextData's buffers are allocated and released
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
- 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
Resolution Note:
Fixed by another internal issue: UUM-117495: Mem leak in render graph compilation cache