Page MenuHome

Crash on adding a Point Light to the Scene and switching to rendered view (Eevee)
Needs Triage, NormalPublic

Description

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92

Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: rB02948a2cab44

Short description of error
First occured in 2.91
I add a point light (the ninth light object in the scene all in all), switch to rendered view in Eevee and Blender crashes. In addition, each time *all* of my enabled and installed add-ons are gone. With the external ones, I have to actually re-install them. That way, I can at least say that it also crashes the same way with all external add-ons switched off or better uninstalled (involuntarily), because as concerns add-ons, Blender is basically swiped clean after the crash.
I updated to 2.92 to check if the crash happens, here, too. It does. I updated my graphics card driver and my system is up to date as of writing this.
I contacted two guys on BlenderChat and one person experienced a crash with the scene in question on a mac, while another person on Linux did not.

Exact steps for others to reproduce the error
In the attached file, add a point light to the bottom of bespin station (called "station" in the outliner), switch to rendered view on Eevee. I did add several point lights on a default blend file and experienced no crashes, so sorry I can't be more specific. I hope you can reproduce the behaviour with the attached file.

Event Timeline

I cannot reproduce this on Linux. My guess is that this might be related to the EEVEE limitations regarding lights (https://docs.blender.org/manual/en/latest/render/eevee/limitations.html).

Hi there,

thanks for your reply!
Your experience then is the same as the one guy on Blender Chat who also was on Linux. The other one on a mac had the scene crashing on him, too.

I wonder which of the limitations which are mentioned on the page you linked to, my scene in the appended file surpassed? I have not counted the faces I assigned an emmissive shader to - do those count as one of the 128 lights, too? And if those faces count, is that "1 emissive face = 1 light"? If yes, I could count the faces and the lights and see if it is the number of lights...

I am not sure. Even if you were to surpass one of the limits, Blender should not crash. @Clément Foucault (fclem) can you reproduce this? Do you know what could be going on here?

Robert Guetzkow (rjg) changed the task status from Needs Triage to Needs Information from User.Mar 29 2021, 8:05 PM

Since we have trouble reproducing the issue, could you please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

Hi, thank you for your help!
BTW, this time around all my installed or enabled add-ons were still around after the crash happened and I restarted blender. Don't know why that changed, but I'm happy about that...
EDIT: out of curiosity I just looked in the attached files (not that I knew what any of the contents mean) and I can't tell why the debug_output is empty. I followed the instructions, sry. Is that significant?

Falk David (filedescriptor) changed the task status from Needs Information from User to Needs Triage.Apr 2 2021, 5:43 PM