Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0b1
Issue ID
1078614
Regression
No
[GPU PLM] [Crash] Memory leak and crash after switching lightmapper to 'Progressive GPU' when baking on GeForce 640M
Prerequisites: pull the repro project from here: https://ono.unity3d.com/test-data/gi-tests/LightmappedTrees
Steps to repro:
1. Open downloaded project and 'Terrain-medium' scene on a laptop with GeForce;
2. In the Lighting window switch Lightmapper to 'Progressive GPU';
3. In the Lighting window click "Generate Lighting" button;
4. When Lightmapper switches back to 'Progressive CPU', switch Lightmapper back to 'Progressive GPU';
5. Repeat step 4.
Expected result:
Lightmapper is switched to Progressive CPU and Editor doesn't crash or throw errors.
Actual result:
Editor crashes without BugReporter and with empty stacktrace. See attached video.
Notes:
- Reproducible in 2019.1.0a1, 2018.3.0b1;
- Reproducible in Windows 10;
- Reproducible only when baking on GeForce 640M with 2GB of VRAM; not reproducible on GeForce GTX 1070.
-
MarkeMark1972
May 22, 2019 08:11
I hit this issue this week. A temporary solution for me was to copy the project to a PC with more GPU memory and then switching the Lightmapper option in the General Lighting panel back to Progressive CPU.
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
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
- Audio Mixer does not change volume when lowering volume on an Audio Mixer loaded from AssetBundles
- Error “Value cannot be null. Parameter name: key UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” thrown and Addressables build fails when "Include in Build" is disabled and using Addressables For Android package
Resolution Note:
Minimal VRAM requirement for GPU Lightmapper has been increased to 4GB, thus, this bug seems to no longer be relevant.