Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.3.1p3
Issue ID
764734
Regression
No
Using a particular light cookie leaks huge amounts of virtual memory and logs 'Shadowmap already exists in the cache' errors
When a particular light cookie is assigned to a light, errors are thrown each time view is updated (clicking on Inspector items, panning and rotating, or when in play mode).
Steps to reproduce:
1) Open the attached project (cookieIssue.zip).
2) Play the 'Main' scene.
Errors are logged in the Console:
Assertion failed on expression: 'mainDirShadowLight != shadowMap.light'
Shadowmap already exists in the cache
Using Instruments on OSX shows that around 16GB of virtual memory is used (virtual memory is not shown in Activity Monitor FYI). IOKit is responsible for the leak. The editor becomes fully unresponsive after some time. The issue goes away when the cookie is removed from the directional light named 'CookieEverythingDirectionalLight'. The leak also occurs on iOS and OS terminates the app after a few seconds.
Reproduced on:
5.6.0a2, 5.5.0f1, 5.4.3f1, 5.3.7p1, 5.2.4f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment