Eevee shading modes crash Blender #80005

New Issue

Ovionis · 2020-08-22T05:15:10+02:00

Ovionis commented

2020-08-22 05:15:10 +02:00

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

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-21 19:33, hash: a1f54be042
Worked: 2020-08-13 275f1039d2

Entering Material/Shaded modes, which uses Eevee rendering, crashes Blender.
No special case/setup/scenario, just this version and my (un-changed) hardware.

Address : 0x00007FF71B053775
Module  : blender.exe
Thread  : 00003710
Writing: C:\Users\-\AppData\Local\Temp\blender.crash.txt```

[blender.crash.txt](https://archive.blender.org/developer/F8802363/blender.crash.txt)

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-21 19:33, hash: `a1f54be042` Worked: 2020-08-13 `275f1039d2` Entering Material/Shaded modes, which uses Eevee rendering, crashes Blender. No special case/setup/scenario, just this version and my *(un-changed)* hardware. ```Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF71B053775 Module : blender.exe Thread : 00003710 Writing: C:\Users\-\AppData\Local\Temp\blender.crash.txt``` [blender.crash.txt](https://archive.blender.org/developer/F8802363/blender.crash.txt)

Ovionis commented

2020-08-22 05:15:10 +02:00

Added subscriber: @Phigon

sbchild commented

2020-08-22 09:28:24 +02:00

Added subscriber: @sbchild

sbchild commented

2020-08-22 09:34:11 +02:00

same issue.

System Information
Operating system: Linux-5.7.15.a-1-hardened-x86_64-with-arch-Arch-Linux 64 Bits
Graphics card: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.57

Blender Version
2.91.0 Alpha, branch: master, commit date: 2020-08-21 23:42, hash: e26301f4d1

blender.crash.txt

same issue. **System Information** Operating system: Linux-5.7.15.a-1-hardened-x86_64-with-arch-Arch-Linux 64 Bits Graphics card: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.57 **Blender Version** 2.91.0 Alpha, branch: master, commit date: 2020-08-21 23:42, hash: `e26301f4d1` [blender.crash.txt](https://archive.blender.org/developer/F8802691/blender.crash.txt)

Christoph commented

2020-08-22 14:36:12 +02:00

Added subscriber: @ChrisGraz

Christoph commented

2020-08-22 14:36:12 +02:00

same on windows:
blender.crash.txt
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-21 19:33, hash: a1f54be042

same on windows: [blender.crash.txt](https://archive.blender.org/developer/F8803262/blender.crash.txt) Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-21 19:33, hash: `a1f54be042`

Wykrhm Reddy commented

2020-08-22 17:27:37 +02:00

Added subscriber: @Wyk

Wykrhm Reddy commented

2020-08-22 17:27:37 +02:00

Can confirm. Not just Eevee. Just entering Material Preview or Rendered mode crashes the entire app. Critical bug.

Ovionis commented

2020-08-22 21:11:24 +02:00

In #80005#1000679, @Wyk wrote:
Can confirm. Not just Eevee. Just entering Material Preview or Rendered mode crashes the entire app. Critical bug.

That is Eevee.

> In #80005#1000679, @Wyk wrote: > Can confirm. Not just Eevee. Just entering Material Preview or Rendered mode crashes the entire app. Critical bug. That is Eevee.

Wykrhm Reddy commented

2020-08-22 21:15:02 +02:00

In #80005#1000761, @Phigon wrote:

In #80005#1000679, @Wyk wrote:
Can confirm. Not just Eevee. Just entering Material Preview or Rendered mode crashes the entire app. Critical bug.

That is Eevee.

Eevee is one of the render engines. Cycles is the other. Both have Material Previews and Rendered Modes. The crash is related to triggering the Material Preview or Rendered mode panel. Irrespective of which Render engine you are on. So it isn't specific to one engine. It's related to the modes themselves.

> In #80005#1000761, @Phigon wrote: >> In #80005#1000679, @Wyk wrote: >> Can confirm. Not just Eevee. Just entering Material Preview or Rendered mode crashes the entire app. Critical bug. > > That is Eevee. Eevee is one of the render engines. Cycles is the other. Both have Material Previews and Rendered Modes. The crash is related to triggering the Material Preview or Rendered mode panel. Irrespective of which Render engine you are on. So it isn't specific to one engine. It's related to the modes themselves.

Georg K commented

2020-08-22 23:29:30 +02:00

Added subscriber: @georgK

Pablo Dobarro commented

2020-08-23 00:59:56 +02:00

Added subscriber: @PabloDobarro

Pablo Dobarro commented

2020-08-23 01:01:16 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Ovionis commented

2020-08-23 07:52:13 +02:00

In #80005#1000762, @Wyk wrote:

In #80005#1000761, @Phigon wrote:

In #80005#1000679, @Wyk wrote:
Can confirm. Not just Eevee. Just entering Material Preview or Rendered mode crashes the entire app. Critical bug.

That is Eevee.

Eevee is one of the render engines. Cycles is the other. Both have Material Previews and Rendered Modes. The crash is related to triggering the Material Preview or Rendered mode panel. Irrespective of which Render engine you are on. So it isn't specific to one engine. It's related to the modes themselves.

Cycles doesn't have a different rendering mode. Cycles is a ray/path tracing render engine or unbiased render engine. Eevee is a biased render engine (I believe glsl but that's irrelevant).

There are 3 render engines in Blender.
There is Cycles which does the photorealistic lighting/GI.
There is Eevee which tries to mimic that realism but faster with shortcuts.
There is Workbench which renders whenever neither of those two specific engines are running.

Every other engine/addon (Vray/Octane/Beer/etc) fills the same slot as Cycles.

This is not isolated to having Eevee set as your current render engine. It is isolated to starting the Eevee render engine.

The different rendering modes (those 4 buttons in the header), don't have anything to do with selecting an engine (or rather, enabling a "sub mode" of the engine). The 2 on the left, use Workbench. The 3rd uses Eevee. The 4th uses what you set as your render engine.
If you use Eevee, the 4th will use Eevee.
If you use Cycles, the 4th will use Cycles.
If you use Redshift, the 4th will use Redshift.
If you use Workbench, there won't be a 3rd/4th because you're already using workbench (there will only be 3 buttons, the 3rd which is Eevee, will be disabled).

> In #80005#1000762, @Wyk wrote: >> In #80005#1000761, @Phigon wrote: >>> In #80005#1000679, @Wyk wrote: >>> Can confirm. Not just Eevee. Just entering Material Preview or Rendered mode crashes the entire app. Critical bug. >> >> That is Eevee. > > Eevee is one of the render engines. Cycles is the other. Both have Material Previews and Rendered Modes. The crash is related to triggering the Material Preview or Rendered mode panel. Irrespective of which Render engine you are on. So it isn't specific to one engine. It's related to the modes themselves. Cycles doesn't have a different rendering mode. Cycles is a ray/path tracing render engine or unbiased render engine. Eevee is a biased render engine *(I believe glsl but that's irrelevant)*. There are 3 render engines in Blender. There is Cycles which does the photorealistic lighting/GI. There is Eevee which tries to mimic that realism but faster with shortcuts. There is Workbench which renders whenever neither of those two specific engines are running. Every other engine/addon (Vray/Octane/Beer/etc) fills the same slot as Cycles. This is not isolated to having Eevee set as your current render engine. It is isolated to starting the Eevee render engine. The different rendering modes (those 4 buttons in the header), don't have anything to do with selecting an engine (or rather, enabling a "sub mode" of the engine). The 2 on the left, use Workbench. The 3rd uses Eevee. The ***4th*** uses what you set as your render engine. If you use Eevee, the 4th will use Eevee. If you use Cycles, the 4th will use Cycles. If you use Redshift, the 4th will use Redshift. If you use Workbench, there won't be a 3rd/4th because you're already using workbench *(there will only be 3 buttons, the 3rd which is Eevee, will be disabled)*.

Jonathan Mielke commented

2020-08-23 10:33:25 +02:00

Added subscriber: @JSM

Wykrhm Reddy commented

2020-08-23 10:39:02 +02:00

In #80005#1000892, @Phigon wrote:

In #80005#1000762, @Wyk wrote:

In #80005#1000761, @Phigon wrote:

In #80005#1000679, @Wyk wrote:
Can confirm. Not just Eevee. Just entering Material Preview or Rendered mode crashes the entire app. Critical bug.

That is Eevee.

Eevee is one of the render engines. Cycles is the other. Both have Material Previews and Rendered Modes. The crash is related to triggering the Material Preview or Rendered mode panel. Irrespective of which Render engine you are on. So it isn't specific to one engine. It's related to the modes themselves.

Cycles doesn't have a different rendering mode. Cycles is a ray/path tracing render engine or unbiased render engine. Eevee is a biased render engine (I believe glsl but that's irrelevant).

There are 3 render engines in Blender.
There is Cycles which does the photorealistic lighting/GI.
There is Eevee which tries to mimic that realism but faster with shortcuts.
There is Workbench which renders whenever neither of those two specific engines are running.

Every other engine/addon (Vray/Octane/Beer/etc) fills the same slot as Cycles.

This is not isolated to having Eevee set as your current render engine. It is isolated to starting the Eevee render engine.

The different rendering modes (those 4 buttons in the header), don't have anything to do with selecting an engine (or rather, enabling a "sub mode" of the engine). The 2 on the left, use Workbench. The 3rd uses Eevee. The 4th uses what you set as your render engine.
If you use Eevee, the 4th will use Eevee.
If you use Cycles, the 4th will use Cycles.
If you use Redshift, the 4th will use Redshift.
If you use Workbench, there won't be a 3rd/4th because you're already using workbench (there will only be 3 buttons, the 3rd which is Eevee, will be disabled).

Ah. Thanks for explaining that. I always thought the modes were individual elements that have different functionality depending on what engine the UI is currently set to. But it does make sense that the Material Preview uses Eevee irrespective of what the render engine is and that affecting only the Rendered mode.

What I still don't get though is .. if the issue with Eevee, then why does Rendered also cause a crash when the engine is set to Cycles?

> In #80005#1000892, @Phigon wrote: >> In #80005#1000762, @Wyk wrote: >>> In #80005#1000761, @Phigon wrote: >>>> In #80005#1000679, @Wyk wrote: >>>> Can confirm. Not just Eevee. Just entering Material Preview or Rendered mode crashes the entire app. Critical bug. >>> >>> That is Eevee. >> >> Eevee is one of the render engines. Cycles is the other. Both have Material Previews and Rendered Modes. The crash is related to triggering the Material Preview or Rendered mode panel. Irrespective of which Render engine you are on. So it isn't specific to one engine. It's related to the modes themselves. > > Cycles doesn't have a different rendering mode. Cycles is a ray/path tracing render engine or unbiased render engine. Eevee is a biased render engine *(I believe glsl but that's irrelevant)*. > > There are 3 render engines in Blender. > There is Cycles which does the photorealistic lighting/GI. > There is Eevee which tries to mimic that realism but faster with shortcuts. > There is Workbench which renders whenever neither of those two specific engines are running. > > Every other engine/addon (Vray/Octane/Beer/etc) fills the same slot as Cycles. > > This is not isolated to having Eevee set as your current render engine. It is isolated to starting the Eevee render engine. > > The different rendering modes (those 4 buttons in the header), don't have anything to do with selecting an engine (or rather, enabling a "sub mode" of the engine). The 2 on the left, use Workbench. The 3rd uses Eevee. The ***4th*** uses what you set as your render engine. > If you use Eevee, the 4th will use Eevee. > If you use Cycles, the 4th will use Cycles. > If you use Redshift, the 4th will use Redshift. > If you use Workbench, there won't be a 3rd/4th because you're already using workbench *(there will only be 3 buttons, the 3rd which is Eevee, will be disabled)*. Ah. Thanks for explaining that. I always thought the modes were individual elements that have different functionality depending on what engine the UI is currently set to. But it does make sense that the Material Preview uses Eevee irrespective of what the render engine is and that affecting only the Rendered mode. What I still don't get though is .. if the issue with Eevee, then why does Rendered also cause a crash when the engine is set to Cycles?

Christoph commented

2020-08-23 11:04:59 +02:00

Rendered mode with cycles is working at my system.

Ovionis commented

2020-08-23 13:14:28 +02:00

In #80005#1000938, @ChrisGraz wrote:

Rendered mode with cycles is working at my system.

That is irrelevant to this report.
(unless your point is to re-specify the crash does not happen with just anyrendering)

> In #80005#1000938, @ChrisGraz wrote: > > Rendered mode with cycles is working at my system. That is irrelevant to this report. *(unless your point is to re-specify the crash does not happen with just **any**rendering)*

Christoph commented

2020-08-23 13:47:18 +02:00

Thats my point: This bug only happens with eevee on my system.

Was commenting to Wykrhm Reddy:

What I still don't get though is .. if the issue with Eevee, then why does Rendered also cause a crash when the engine is set to Cycles?

Thats my point: This bug only happens with eevee on my system. Was commenting to Wykrhm Reddy: > What I still don't get though is .. if the issue with Eevee, then why does Rendered also cause a crash when the engine is set to Cycles?

Luke Graybill commented

2020-08-23 15:11:18 +02:00

Added subscriber: @Luke.Coop

Jonathan Mielke commented

2020-08-23 15:18:00 +02:00

This seems to be fixed for me with e4932d1167 commit.

This seems to be fixed for me with e4932d1167 commit.

Petter Lundh commented

2020-08-23 21:05:26 +02:00

Added subscriber: @PetterLundh

Ovionis commented

2020-08-24 07:44:04 +02:00

In #80005#1001010, @ChrisGraz wrote:
Was commenting to Wykrhm Reddy:

kek, I did not see their post. Makes sense.

In #80005#1000928, @Wyk wrote:
What I still don't get though is .. if the issue with Eevee, then why does Rendered also cause a crash when the engine is set to Cycles?

I think you're literally the only person on this page with that issue.

If you can't get cycle's path tracing viewport running, you're having a separate issue from the rest of us.

> In #80005#1001010, @ChrisGraz wrote: > Was commenting to Wykrhm Reddy: kek, I did not see their post. Makes sense. > In #80005#1000928, @Wyk wrote: > What I still don't get though is .. if the issue with Eevee, then why does Rendered also cause a crash when the engine is set to Cycles? I think you're literally the only person on this page with that issue. If you can't get cycle's path tracing viewport running, you're having a separate issue from the rest of us.

Clément Foucault commented

2020-08-24 12:31:04 +02:00

Closed as duplicate of #80034

Clément Foucault closed this issue

2020-08-24 12:31:04 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Eevee shading modes crash Blender #80005