Search Issue Tracker
Duplicate
Duplicate in 2019.3.X
Votes
0
Found in
2019.3.0f6
2020.1.0a20
Issue ID
1217998
Regression
Yes
Major memory leak occurs when instantiating or dragging a Particle System Prefab with Light module into the Scene view
How to reproduce:
1. Open user-submitted project (ShadowMapRepro_Stripped)
2. Enter Play Mode
3. Switch to Scene View
4. Make sure the particles that are already in the Scene are visible
5. Drag the Assets/_Data/_FX/Spells/po_Fireball.prefab into the Scene View
Expected result: no errors are thrown, no memory leak occurs
Actual result: 'Shadowmap already exists in the cache' errors are printed in the Console window, Texture allocated memory continuously increases
Reproducible with: 2019.3.0f6, 2020.1.0a20, 2020.1.0a23
Not reproducible with: 2018.4.17f1, 2019.2.21f1, 2019.3.0f5, 2020.1.0a1, 2020.1.0a19
Could not test with: 2017.4.36f1(project incompatibility issues)
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
This is a duplicate of issue #1217809