Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2020.1.3f1
2020.2.0a21
Issue ID
1271626
Regression
Yes
[OSX] Crash on 'Preparing Bake' stage when rebaking GI after changing lighting settings and clearing baked data
Steps to repro:
1. Open the attached project and 'ProgressiveLightmappingExample' scene on OSX;
2. In the Lighting window press the dropdown near the "Generate Lighting" button and select "Clear baked data";
3. In the Lighting window press "Generate Lighting" button;
4. When the GI baking is finished, change some lighting-related settings (e.g. type '1' into "Direct Samples" field);
5. In the Lighting window press "Generate Lighting" button.
Expected result:
GI baking finishes without errors.
Actual result:
Editor crashes instantly. The stacktrace is meaningless. See attached video.
Regression introduced in Versions 2020.1.3f1 and 2020.2.0a21.
Notes:
- Reproducible in Version 2020.2.0a21, 2020.1.3f1;
- Not reproducible in 2020.2.0a20, 2020.1.2f1, 2019.4.9f1;
- Reproducible only on OSX, not reproducible on Windows;
- Reproducible only when clearing baked GI after initial bake;
- Reproducible only in the attached project; not reproducible in the URP sample scene and in the CornellBox project;
- Reproducible only when baking with PLM; not reproducible when baking with Enlighten;
- Could not test on GPU PLM because the GI bake cannot be completed (known issue);
- Sometimes when the crash happens (1 of 5 times approximately), the Editor freezes, and the only way to close it is to restart the machine (killing the process from the macOS Activity Monitor has no effect). However, the frozen Editor doesn't freeze the whole OS.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Cascaded Shadows do not have a falloff in Player when the Player is built not in Development Mode
- Grid in animation preview window is rendered on top of the object
- WebGPU Graphics.RenderPrimitives fails on MeshTopology.Quads with Validation errors when exceeding 64k vertices
- Task status is "WaitingForActivation" when awaiting a faulted task inside that task
- 0 is returned when any output from Split Node is input into the Lerp Node
Add comment