CRASH when click "Viewport Shading - Rendered" icon #66732

Closed
opened 2019-07-12 05:38:20 +02:00 by Don · 26 comments

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 10.18.14.5067

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 11:00, hash: d663048696
Worked: (optional)

Short description of error
When click "Viewport Shading - Rendered" icon, Blender 2.8 crashes immediately.

Exact steps for others to reproduce the error
When clicking "Viewport Shading - Rendered" icon (between "Viewport Shading - Look Dev" and "Viewport Shading > dropdown" arrow icon, Blender 2.8 crashes immediately.

3. Viewport shading crash.PNG

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 10.18.14.5067 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 11:00, hash: `d663048696` Worked: (optional) **Short description of error** When click "Viewport Shading - Rendered" icon, Blender 2.8 crashes immediately. **Exact steps for others to reproduce the error** When clicking "Viewport Shading - Rendered" icon (between "Viewport Shading - Look Dev" and "Viewport Shading > dropdown" arrow icon, Blender 2.8 crashes immediately. ![3. Viewport shading crash.PNG](https://archive.blender.org/developer/F7598976/3._Viewport_shading_crash.PNG)
Author

Added subscriber: @donhartig

Added subscriber: @donhartig

#66737 was marked as duplicate of this issue

#66737 was marked as duplicate of this issue

#66738 was marked as duplicate of this issue

#66738 was marked as duplicate of this issue

#66739 was marked as duplicate of this issue

#66739 was marked as duplicate of this issue
Author

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Don closed this issue 2019-07-12 05:42:40 +02:00
Don self-assigned this 2019-07-12 05:42:40 +02:00
Author

Sorry, this one can not be reproduced consistently. Was happening every time (at least in Eevee mode") but now seems to be working without crashing.

Sorry, this one can not be reproduced consistently. Was happening every time (at least in Eevee mode") but now seems to be working without crashing.
Author

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Don reopened this issue 2019-07-12 07:36:22 +02:00
Author

Sorry, this is still happening at least 50% of the time when the "Rendered" viewport shader is selected so I changed this bug back to "Open".

Sorry, this is still happening at least 50% of the time when the "Rendered" viewport shader is selected so I changed this bug back to "Open".

Added subscriber: @ideasman42

Added subscriber: @ideasman42

Added subscriber: @ZedDB

Added subscriber: @ZedDB

I'll merge all crash reports here as it seems like this is probably your GPU drivers that are at fault.

Does it help if you run blender with --debug-gpu-force-workarounds ?
What is the output if you run blender with --debug-gpu?

I'll merge all crash reports here as it seems like this is probably your GPU drivers that are at fault. Does it help if you run blender with `--debug-gpu-force-workarounds` ? What is the output if you run blender with `--debug-gpu`?
Author

Hi Sebastian,

Updated all GPU drivers for Intel 4600 yesterday so perhaps a different reason.

OK, I ran it with --debug-gpu and here is the output:

Output.PNG

Hope this helps.

Hi Sebastian, Updated all GPU drivers for Intel 4600 yesterday so perhaps a different reason. OK, I ran it with --debug-gpu and here is the output: ![Output.PNG](https://archive.blender.org/developer/F7601888/Output.PNG) Hope this helps.

Did it help with the workarounds flag?

Did it help with the workarounds flag?
Author

Hi, just finished with workarounds flag. It worked for

  1. Adding texture CRASH, and
  2. Sliding "Metallic" property to 100% (1.0)

BUT not for:

  1. Selecting custom-installed HDRI - it appears in the HDRI list section but still crashes when the custom-installed HDRI is clicked. Default HDRIs do not lead to crash.

Here is the output when crashes in case #3, DESPITE using --debug-gpu-force-workarounds:

image.png

UPDATE: Immediate crashing when clicking on "Rendered" also seems to have stopped with --debug-gpu-force-workarounds flag.

So now it's only the one error that persists, i.e. #3: user-installed HDRI map causing crash when selected from HDRI dropdown menu with "Look Dev" selected. Here's a screenshot:

custom HDRI crash.PNG

Hi, just finished with workarounds flag. It worked for 1. Adding texture CRASH, and 2. Sliding "Metallic" property to 100% (1.0) BUT not for: 3. Selecting custom-installed HDRI - it appears in the HDRI list section but still crashes when the custom-installed HDRI is clicked. Default HDRIs do not lead to crash. Here is the output when crashes in case #3, DESPITE using --debug-gpu-force-workarounds: ![image.png](https://archive.blender.org/developer/F7602029/image.png) UPDATE: Immediate crashing when clicking on "Rendered" also seems to have stopped with --debug-gpu-force-workarounds flag. So now it's only the one error that persists, i.e. #3: user-installed HDRI map causing crash when selected from HDRI dropdown menu with "Look Dev" selected. Here's a screenshot: ![custom HDRI crash.PNG](https://archive.blender.org/developer/F7602178/custom_HDRI_crash.PNG)

How much video memory do you have? I'm guessing that you simply run out if VRAM in that case.

How much video memory do you have? I'm guessing that you simply run out if VRAM in that case.
Author

Video memory is still the exact same vid memory I have been using for more than a year with 2.79 with ZERO crashes ever.
video memory.PNG
I could not find an specific minimum requirements for 2.80. If the requirements are exactly the same as for 2.79, then surely it should not be crashing every 2 minutes on my current specs as this has never happened with daily use with 2.79.

Or am I missing something?

If the requirements have changed for 2.8, could you perhaps point out what is now required?

Thanks.

Video memory is still the exact same vid memory I have been using for more than a year with 2.79 with ZERO crashes ever. ![video memory.PNG](https://archive.blender.org/developer/F7602278/video_memory.PNG) I could not find an specific minimum requirements for 2.80. If the requirements are exactly the same as for 2.79, then surely it should not be crashing every 2 minutes on my current specs as this has never happened with daily use with 2.79. Or am I missing something? If the requirements have changed for 2.8, could you perhaps point out what is now required? Thanks.

I was specifically talking about the HDRI issue. The others are simply drivers issues that are worked around with the --debug-gpu-force-workarounds flag.

Does the HDRI still still crash if you limit texture sizes?:
screenshot.png

I was specifically talking about the HDRI issue. The others are simply drivers issues that are worked around with the `--debug-gpu-force-workarounds` flag. Does the HDRI still still crash if you limit texture sizes?: ![screenshot.png](https://archive.blender.org/developer/F7602464/screenshot.png)

Added subscriber: @Ghostil

Added subscriber: @Ghostil
https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/ See this.

Added subscriber: @dark999

Added subscriber: @dark999
@donhartig ![Screenshot_20190712_131917.png](https://archive.blender.org/developer/F7602773/Screenshot_20190712_131917.png)
Author

OK, tried everything I can think of vis. the HDRI issue. I guess you must be right although HDRIs worked in cycles in 2.79 with the same hardware.

Yes, also tried limiting screen size on all settings, but still crashes when try to select HDRIs other than the default ones.
However I discovered one thing: When I install smaller HDRIs, there does not appear to be a problem. The previous ones I was trying were all 16K.

One final question: the --debug-gpu-force-workarounds flag seems to have solved 3 out of the 4 problems but does this mean that in order to use 2.8 with my current hardware configuration, I will have to continue using this flag indefinitely? I.e. does 2.8 require a discrete graphics card to run without crashes if the flag is not used?

Thanks.

OK, tried everything I can think of vis. the HDRI issue. I guess you must be right although HDRIs worked in cycles in 2.79 with the same hardware. Yes, also tried limiting screen size on all settings, but still crashes when try to select HDRIs other than the default ones. However I discovered one thing: When I install smaller HDRIs, there does not appear to be a problem. The previous ones I was trying were all 16K. One final question: the --debug-gpu-force-workarounds flag seems to have solved 3 out of the 4 problems but does this mean that in order to use 2.8 with my current hardware configuration, I will have to continue using this flag indefinitely? I.e. does 2.8 require a discrete graphics card to run without crashes if the flag is not used? Thanks.
Don was unassigned by Sebastian Parborg 2019-07-12 14:10:35 +02:00
Jeroen Bakker was assigned by Sebastian Parborg 2019-07-12 14:10:35 +02:00

We will add your GPU to the automatic workaround list eventually.

We will add your GPU to the automatic workaround list eventually.
Author

OK, thanks a lot. The link sent by @Ghostil indicates that my GPU is supported by Blender 2.80. Hope things will be running more smoothly soon.

I would like to thank you guys for your hard work on this project and your lightning-fast responsiveness. You are truly even more effective than any paid online service I have ever had to deal with and I have just published on Blendernation in which I hope to bring more attention and gratitude to the phenomenal work you are doing.

Looking forward to next update.

~Don

OK, thanks a lot. The link sent by @Ghostil indicates that my GPU is supported by Blender 2.80. Hope things will be running more smoothly soon. *I would like to thank you guys for your hard work on this project and your lightning-fast responsiveness. You are truly even more effective than any paid online service I have ever had to deal with and I have just published on Blendernation in which I hope to bring more attention and gratitude to the phenomenal work you are doing.* Looking forward to next update. ~Don

@donhartig as you had reported, you are under minimum requierement hardware, your maximum vodeo memory shuld be 1824M instead minimun requiered of 2048M, your picture show you use 192M video memory

@donhartig as you had reported, you are under minimum requierement hardware, your maximum vodeo memory shuld be 1824M instead minimun requiered of 2048M, your picture show you use 192M video memory
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
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
6 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#66732
No description provided.