Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0a9
2019.2.0a10
Issue ID
1141511
Regression
Yes
[Linux] Crash in ShaderCompiler if lightmapping is left on auto-generate
To reproduce:
1) Just Create New Project
Result: It crashes a bit after launching due to ShaderCompiler error
Only reproduced in 2019.2.0a9, 2019.2.0a10 on CentOS 7 running Intel HD 615
Not reproduced in 2019.2.0a8, 2019.1.0b9
Also not reproduced on Ubuntu Intel HD 5500 machine
Workaround: If using an older version and removing "Auto-generate" from Lighting Options, the crash doesn't happen, even in the a9+
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (2019.3.X):
Our analysis points to this being a driver issue with the Intel HD card. At this time, the Unity editor on Linux only supports NVIDIA devices with official drivers or AMD devices with up-to-date Mesa drivers.