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
- “Open” button in Inspector does not function for certain Assets
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
Add comment