Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b2
Issue ID
905026
Regression
Yes
Crashed after building on standalone player, possible memory leak
Reproduction steps:
1. Open project attached(case_904483-unity_progressive_lightmapper_test.zip).
2. Open scene "Shadowmask"
3. Build for standalone player.
Expected result: It will succeed.
Actual result: After it succeeds, memory leak appears and due to that, Unity crashes.
Note: Some errors used to appear like "Clustering failed due to lack of memory" and it needed like 32gb of it. They disappeared after few restarts.
Reproduced on: 2017.1.0b2
Worked fine on: 2017.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
- The build size is larger when Models have Animation Type set to Generic
Add comment