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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment