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
- Particles are respawned when selecting different Particle System child GameObjects
- A gap at the bottom of the screen appears when entering Play mode in full screen
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
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.