Crash in light preferences #76137

Closed
opened 2020-04-26 23:35:42 +02:00 by Hayden Green · 20 comments

System Information
Operating system: Mac 06 10.13.6
Graphics card: Radeon R9 M370X

Blender Version
2.82.7a

Short description of error
Import HDRI > Crash

Exact steps for others to reproduce the error

  1. Set Viewport Shading to Material Preview
  2. Open the Viewport Shading options and click on the cog to show the light preferences.
  3. Blender will crash

Happens in any file.

**System Information** Operating system: Mac 06 10.13.6 Graphics card: Radeon R9 M370X **Blender Version** 2.82.7a **Short description of error** Import HDRI > Crash **Exact steps for others to reproduce the error** 1. Set Viewport Shading to *Material Preview* 2. Open the Viewport Shading options and click on the cog to show the light preferences. 3. Blender will crash Happens in any file.
Author

Added subscriber: @skank

Added subscriber: @skank
Robert Guetzkow changed title from Import HDRI > Crash to Crash in light preferences 2020-04-27 12:46:38 +02:00

Added subscriber: @rjg

Added subscriber: @rjg

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

Please make sure that your graphics driver is the most recent version. Should the issue still occur with current drivers, save the system information through Help > Save System Info in Blender. Additionally start Blender in debug mode from the terminal through blender --debug --debug-cycles > blender_debug_output.txt 2>&1 and try to make it crash again. Attach both files to your bug report by clicking on the upload button as shown in the screenshot below.

Have you previously modified the light preferences before this issue occurred, e.g. by installing custom studio lights, matcaps or HDRIs?

2019_12_04_upload_icon_developer_blender_org.png

Please make sure that your graphics driver is the most recent version. Should the issue still occur with current drivers, save the system information through *Help > Save System Info* in Blender. Additionally start Blender in debug mode from the terminal through `blender --debug --debug-cycles > blender_debug_output.txt 2>&1` and try to make it crash again. Attach both files to your bug report by clicking on the upload button as shown in the screenshot below. Have you previously modified the light preferences before this issue occurred, e.g. by installing custom studio lights, matcaps or HDRIs? ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)
Author

Hello, regarding driver updates, to my understanding that is dealt with the MacOS updates and not discretely so I would have the lastest I could have for my OS version.

No I have not previously modified light preferences

Files you requested can be sent seperately.

Hello, regarding driver updates, to my understanding that is dealt with the MacOS updates and not discretely so I would have the lastest I could have for my OS version. No I have not previously modified *light preferences* Files you requested can be sent seperately.

@skank That is correct, the driver version is tied to the OS version on macOS. What do you mean by sending them separately?

@skank That is correct, the driver version is tied to the OS version on macOS. What do you mean by sending them separately?
Author

In #76137#918664, @rjg wrote:
@skank What do you mean by sending them separately?

Hello Robert, it's re sending the system info and debug files you requested.

> In #76137#918664, @rjg wrote: > @skank What do you mean by sending them separately? Hello Robert, it's re sending the `system info` and `debug` files you requested.

@skank I've understood that, I'm assuming you meant that you don't want to upload them on the bug tracker?

@skank I've understood that, I'm assuming you meant that you don't want to upload them on the bug tracker?
Author

@rjg I'm currently unfamiliar with that process, might be easier to send if that helps.

Out of interest am I the only one reporting this? It's so repeateble I thought it might be a thing.

@rjg I'm currently unfamiliar with that process, might be easier to send if that helps. Out of interest am I the only one reporting this? It's so repeateble I thought it might be a thing.

@skank Simply click on the upload button on the website as shown in the image below or drag-and-drop the files in comment area.

2019_12_04_upload_icon_developer_blender_org.png

Please also test the following:

  • Check if it also crashes when opening the preferences in general (Edit > Preferences) or just in the Lights tab.
  • Check if the issue occurs in the most recent daily build of Blender 2.90 .
  • Check if temporarily loading the factory defaults fixes the issue blender --factory-startup

I can't reproduce it, which is why we need the log files.

@skank Simply click on the upload button on the website as shown in the image below or drag-and-drop the files in comment area. ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png) Please also test the following: - Check if it also crashes when opening the preferences in general (*Edit > Preferences*) or just in the *Lights* tab. - Check if the issue occurs in the most recent [daily build of Blender 2.90 ](https://builder.blender.org/download/). - Check if temporarily loading the factory defaults fixes the issue `blender --factory-startup` I can't reproduce it, which is why we need the log files.
Author

Hello Robert, I have the System Info report ready to send, but the debug mode didn't work for me, tried several times.

Can I mail you the report somewhere and any thoughts on the debug/m?

Hello Robert, I have the System Info report ready to send, but the debug mode didn't work for me, tried several times. Can I mail you the report somewhere and any thoughts on the debug/m?

@skank What exactly didn't work with debug mode? The file will be generated in the current working directory, if you've run the command as is.

You will have to publicly upload the file onto the tracker, as described in the previous comment, since other developers will likely have to take a look as well. There's no point in sending the file only to me, especially since I'm not working on macOS. If this is a platform specific issue, I won't be able to reproduce this anyway.

If you're having privacy concerns, you may redact information from the file. It only contains information about your Blender installation, hardware and driver which are necessary to diagnose issues though.

@skank What exactly didn't work with debug mode? The file will be generated in the current working directory, if you've run the command as is. You will have to publicly upload the file onto the tracker, as described in the previous comment, since other developers will likely have to take a look as well. There's no point in sending the file only to me, especially since I'm not working on macOS. If this is a platform specific issue, I won't be able to reproduce this anyway. If you're having privacy concerns, you may redact information from the file. It only contains information about your Blender installation, hardware and driver which are necessary to diagnose issues though.
Author

OK, I can have a look at the directory to see,

Noted re all else.

OK, I can have a look at the directory to see, Noted re all else.
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

Does this happen on 2.83 ? download from https://builder.blender.org Some material preview bugs were fixed. Some remain, like #74401 (Eevee: Crash upon expanding material preview)
also does the whole computer hang before Blender crashes ?

Also @rjg, Blender executable is some folders deep in the Blender.app container. See #75945#926722 @skank you can also see how to run Blender via console for future use.

Does this happen on 2.83 ? download from https://builder.blender.org Some material preview bugs were fixed. Some remain, like #74401 (Eevee: Crash upon expanding material preview) also does the whole computer hang before Blender crashes ? Also @rjg, Blender executable is some folders deep in the Blender.app container. See #75945#926722 @skank you can also see how to run Blender via console for future use.

@ankitm Looks like you're right, I thought it set the alias automatically on install. How to start Blender from a terminal on macOS is documented in Blender's manual .

@ankitm Looks like you're right, I thought it set the alias automatically on install. How to start Blender from a terminal on macOS is documented in [Blender's manual ](https://docs.blender.org/manual/en/latest/advanced/command_line/launch/macos.html).
Author

@ankitm tested with version 2.83 (2.83 2020-05-01) and cannot repeat the issue— seems like this has been fixed.

@ankitm tested with version 2.83 (2.83 2020-05-01) and cannot repeat the issue— seems like this has been fixed.
Member

Changed status from 'Needs User Info' to: 'Resolved'

Changed status from 'Needs User Info' to: 'Resolved'
Ankit Meel self-assigned this 2020-05-10 06:44:10 +02:00

Added subscriber: @tycse

Added subscriber: @tycse

New user here. I just wanted to comment for anyone else who may experience this issue in the future. The root cause, in my case, was not a "bug" in a previous version of Blender; rather, it was due to me attempting to install an HDRI that was corrupt and/or invalid, unbeknownst to me. I had attempted to install the HDRI through the Light Preferences dialog, resulting in an instant Blender crash. All subsequent attempts to restart Blender and reopen the Light Preferences dialog resulted in an instant crash.

Resolution involves deleting the corrupt HDRI image from the following directory [Windows].

blender_debug_output.txt
IMB_ibImageFromMemory: unknown fileformat
C:\Users<you>\AppData\Roaming\Blender Foundation\Blender<version>\datafiles\studiolights/world/.HDR

New user here. I just wanted to comment for anyone else who may experience this issue in the future. The root cause, in my case, was not a "bug" in a previous version of Blender; rather, it was due to me attempting to install an HDRI that was corrupt and/or invalid, unbeknownst to me. I had attempted to install the HDRI through the Light Preferences dialog, resulting in an instant Blender crash. All subsequent attempts to restart Blender and reopen the Light Preferences dialog resulted in an instant crash. Resolution involves deleting the corrupt HDRI image from the following directory [Windows]. blender_debug_output.txt IMB_ibImageFromMemory: unknown fileformat C:\Users\<you>\AppData\Roaming\Blender Foundation\Blender\<version>\datafiles\studiolights/world/<badHDRFile>.HDR
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#76137
No description provided.