Search Issue Tracker
Fixed in 4.0.0-pre.1
Fixed in 3.0.2-preview
Votes
0
Found in [Package]
3.0.1-preview
Issue ID
1276955
Regression
No
[Terrain Tools] RenderTextures leaked in FilterContext
Will eventually crash the editor or at least interfere with rendering as there will not be enough rendertexture resources to use
repro steps
1. Open Window > Analysis > Profiler
2. Enable memory module (profile modules drop down)
3. Under profile modules drop down, select "Memory" row
4. Set profiler to "Editor" (just left of record button)
5. In bottom window, change Simple > Detailed view
a. to see "Gather object references"
6. Get baseline
a. Click Take sample editor
b. View "Gather object references" tab
c. Examine Scene memory > renderTexture (memory used & ref count)
7. Paint with some texture brushes
a. Raise/lower terrain
b. Create new brush with mask filters (add, abs, etc..)
c. Transform > twist
d. Etc..
8. Update baseline (step 5) and compare
Expected results: Should not see increase in scene memory used or ref counts of scene memory objects
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment