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
- WebGPU errors when CoreCopy shader is used to copy an MSAA texture
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
Add comment