Eevee: Crash upon expanding material preview #74401

New Issue

Ankit Meel · 2020-03-03T15:52:28+01:00

Ankit Meel commented

2020-03-03 15:52:28 +01:00

System Information
Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits
Graphics card: Intel(R) HD Graphics 6000 Intel Inc. 4.1 INTEL-12.10.12

Blender Version
Broken: version: 2.83 (sub 6), branch: pseudomaster, commit date: 2020-03-03 14:06, hash: dcfc399066. This is same as ed29ff944a in master but with little changes in CMakeLists.txt for ccache.

Short description of error
Expanding this Preview hangs the system, & returns

GPU hang occurred, msgtracer returned -1
GPU hang occurred, msgtracer returned -1
(lldb)

Exact steps for others to reproduce the error
open the file, click on preview to open it.

notes

Mac + intel issue, it seems
eevee specific.
https:*pastebin.com/CiRUzzWQ > https:*pastebin.com/uX7eZAgE > https:*pastebin.com/JQD4a0j1 > https:*pastebin.com/WpiL9wdM > https:*pastebin.com/PU43Gx16 > https:*pastebin.com/4HBeb4sU > https:*pastebin.com/ZZV7J6h6 > https:*pastebin.com/xcNMXjfV > https:*pastebin.com/Khyu77tw > https:*pastebin.com/11SBNW3W > https:*pastebin.com/FKBbCRyE > https:*pastebin.com/n4dyYxFS > abort & kill etc.
some experimentation with @mano-wii in https://blender.chat/channel/everyzone. commented the function DRW_uniformbuffer_update in eevee_shadows.c etc.
related & resolved for some/many users: #74174
twitter ehader test-2.blend
system-info.txt

**System Information** Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits Graphics card: Intel(R) HD Graphics 6000 Intel Inc. 4.1 INTEL-12.10.12 **Blender Version** Broken: version: 2.83 (sub 6), branch: pseudomaster, commit date: 2020-03-03 14:06, hash: `dcfc399066`. This is same as `ed29ff944a` in master but with little changes in `CMakeLists.txt` for ccache. **Short description of error** Expanding this Preview hangs the system, & returns ``` GPU hang occurred, msgtracer returned -1 GPU hang occurred, msgtracer returned -1 (lldb) ``` ![image.png](https://archive.blender.org/developer/F8384987/image.png) **Exact steps for others to reproduce the error** open the file, click on preview to open it. **notes** - Mac + intel issue, it seems - eevee specific. - https:*pastebin.com/CiRUzzWQ > https:*pastebin.com/uX7eZAgE > https:*pastebin.com/JQD4a0j1 > https:*pastebin.com/WpiL9wdM > https:*pastebin.com/PU43Gx16 > https:*pastebin.com/4HBeb4sU > https:*pastebin.com/ZZV7J6h6 > https:*pastebin.com/xcNMXjfV > https:*pastebin.com/Khyu77tw > https:*pastebin.com/11SBNW3W > https:*pastebin.com/FKBbCRyE > https:*pastebin.com/n4dyYxFS > abort & kill etc. - some experimentation with @mano-wii in https://blender.chat/channel/everyzone. commented the function `DRW_uniformbuffer_update` in `eevee_shadows.c` etc. - related & resolved for some/many users: #74174 [twitter ehader test-2.blend](https://archive.blender.org/developer/F8383828/twitter_ehader_test-2.blend) [system-info.txt](https://archive.blender.org/developer/F8385003/system-info.txt)

Ankit Meel commented

2020-03-03 15:52:28 +01:00

Added subscribers: @mano-wii, @ankitm

blender-admin commented

2020-03-03 15:52:28 +01:00

#76789 was marked as duplicate of this issue

Germano Cavalcante commented

2020-03-03 15:57:34 +01:00

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

Germano Cavalcante commented

2020-03-03 15:57:34 +01:00

It is also good to inform if this is a regression and which commit introduced this problem.

Brecht Van Lommel commented

2020-03-04 09:26:22 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2020-03-04 09:26:22 +01:00

I can reproduce this crash with Intel Iris Graphics 6000 on macOS 10.15.3.

I'm not sure if this is a regression or not, unlike the comment in #74174#882160 seems to imply, going back to 7e7c927602 does not stop the crash.

So the next step would be to either figure out which commit broke this, or to simplify the .blend file and shader nodes to isolate the problem.

I can reproduce this crash with Intel Iris Graphics 6000 on macOS 10.15.3. I'm not sure if this is a regression or not, unlike the comment in #74174#882160 seems to imply, going back to 7e7c927602 does not stop the crash. So the next step would be to either figure out which commit broke this, or to simplify the .blend file and shader nodes to isolate the problem.

Ankit Meel commented

2020-03-04 12:01:04 +01:00

Added subscriber: @Drawingistmusashi

Ankit Meel commented

2020-03-04 12:01:04 +01:00

I will start bisecting in 2 hrs... and as I had said in the other report, it’s not my file & I cannot don’t know what to edit either. Tagging @DrawingistMushashi for that.

Will also verify once again if log2 commit is working or not.

I will start bisecting in 2 hrs... and as I had said in the other report, it’s not my file & I cannot don’t know what to edit either. Tagging @DrawingistMushashi for that. Will also verify once again if log2 commit is working or not.

Ankit Meel commented

2020-03-04 17:29:22 +01:00

So I jumped 4-5 days each test, reached 2.82 & it's still crashing. Do I check further?
@Drawingistmusashi could you simplify the blend file, remove extraneous elements please ? (keep material properties open, preview closed while saving)
Here's the crash report, if clicking links seems terrible :p

Application Specific Information:
abort() called

Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x00000813

T74401_T74174.txt

- So I jumped 4-5 days each test, reached 2.82 & it's still crashing. Do I check further? - @Drawingistmusashi could you simplify the blend file, remove extraneous elements please ? (keep material properties open, preview closed while saving) - Here's the crash report, if clicking links seems terrible :p ``` Application Specific Information: abort() called Application Specific Signatures: Graphics hardware encountered an error and was reset: 0x00000813 ``` [T74401_T74174.txt](https://archive.blender.org/developer/F8388129/T74401_T74174.txt)

Ankit Meel commented

2020-03-04 19:50:52 +01:00

was browsing GitHub with "application specific signatures"..
https://github.com/buddhi1980/mandelbulber2/issues/538#issuecomment-436699732 see this & two below it.

.. after your latest comment now I'm sure that it is GPU timeout problem. When DE_factor is low and detail level high, there is quite long time to render one tile of image (to process one single job (workgroup) by GPU). Now there is needed to figure out how to disable GPU watchdog on MacOS. On Linux watchdog is disabled by default. On Windows we are disabling it by adding registry entry using regedit.

I was thinking that it is known issue/ expected behaviour but here it goes: when changing viewport shading to material, there is a momentary freeze, also when on default cube, we open this preview in material properties. it seems GPU never recovers from it, in this particular file.

was browsing GitHub with "application specific signatures".. https://github.com/buddhi1980/mandelbulber2/issues/538#issuecomment-436699732 see this & two below it. > .. after your latest comment now I'm sure that it is GPU timeout problem. When DE_factor is low and detail level high, there is quite long time to render one tile of image (to process one single job (workgroup) by GPU). Now there is needed to figure out how to disable GPU watchdog on MacOS. On Linux watchdog is disabled by default. On Windows we are disabling it by adding registry entry using regedit. I was thinking that it is known issue/ expected behaviour but here it goes: when changing viewport shading to material, there is a momentary freeze, also when on default cube, we open this preview in material properties. it seems GPU never recovers from it, in this particular file.

Deckerd Rose commented

2020-03-04 20:09:21 +01:00

I tried opening a file with default cube, Eevee render, from the build bot on February 24th, a322b43e3d , and did still get a crash when attempting to navigate to or change material properties tab. Testing the latest build, same situation, no crash. All settings should be on factory default for both test.

Same results when testing my example file, and it even seems that the current build fixed something I almost brought up about weird latency issues for the freestyle render pass.

I tried opening a file with default cube, Eevee render, from the build bot on February 24th, a322b43e3d08 , and did still get a crash when attempting to navigate to or change material properties tab. Testing the latest build, same situation, no crash. All settings should be on factory default for both test. Same results when testing my example file, and it even seems that the current build fixed something I almost brought up about weird latency issues for the freestyle render pass.

Brecht Van Lommel commented

2020-03-05 11:40:16 +01:00

@ankitm, totally up to you if you want to keep debugging this, but if you were then:

In #74401#885269, @ankitm wrote:

So I jumped 4-5 days each test, reached 2.82 & it's still crashing. Do I check further?

It's probably easiest to test the 2.80 and 2.81 releases downloaded from blender.org.

I will start bisecting in 2 hrs... and as I had said in the other report, it’s not my file & I cannot don’t know what to edit either. Tagging @DrawingistMushashi for that.

What I would do is remove as much as possible until the crash no longer happens. In this particular case, that be removing shader nodes until we find that there is a particular shader node that is problematic, or that things simplify start failing at a certain amount of shader nodes.

@ankitm, totally up to you if you want to keep debugging this, but if you were then: > In #74401#885269, @ankitm wrote: > - So I jumped 4-5 days each test, reached 2.82 & it's still crashing. Do I check further? It's probably easiest to test the 2.80 and 2.81 releases downloaded from blender.org. > I will start bisecting in 2 hrs... and as I had said in the other report, it’s not my file & I cannot don’t know what to edit either. Tagging @DrawingistMushashi for that. What I would do is remove as much as possible until the crash no longer happens. In this particular case, that be removing shader nodes until we find that there is a particular shader node that is problematic, or that things simplify start failing at a certain amount of shader nodes.

Ankit Meel commented

2020-03-05 19:41:34 +01:00

~~Broken~~ working rather: version: 2.80 (sub 75), branch: master, commit date: 2019-07-24 14:22, hash: 507ffee6e1
off for bisecting

![image.png](https://archive.blender.org/developer/F8390131/image.png) ~~Broken~~ working rather: version: 2.80 (sub 75), branch: master, commit date: 2019-07-24 14:22, hash: `507ffee6e1` *off for bisecting*

Ankit Meel commented

2020-03-05 21:46:13 +01:00

Added subscriber: @fclem

Ankit Meel commented

2020-03-05 21:46:13 +01:00

caused by d5002f007e cc: @fclem

caused by d5002f007e cc: @fclem

Ankit Meel commented

2020-03-12 07:45:55 +01:00

#74547 Image texture with this specific configuration cause a crash in EEVEE or material preview

Clément Foucault commented

2020-03-30 20:07:34 +02:00

@ankitm I don't think #74547 is related.
For this report, it looks like the shader is taking a long time to compile and this could mean the drivers choke on it. Can you try simplifying the shader?

I could not reproduce the crash and asan does not find anything anormal.

@ankitm I don't think #74547 is related. For this report, it looks like the shader is taking a long time to compile and this could mean the drivers choke on it. Can you try simplifying the shader? I could not reproduce the crash and asan does not find anything anormal.

Ankit Meel commented

2020-03-31 10:00:09 +02:00

Just found, also happens when clicking this icon to get a list of materials.

Can you try simplifying the shader?

will do .

b555b8dedce058985bfe8c544c8c46ba4821bc1a

Just found, also happens when clicking this icon to get a list of materials. ![Screenshot 2020-03-31 at 13.20.47.png](https://archive.blender.org/developer/F8438610/Screenshot_2020-03-31_at_13.20.47.png) >Can you try simplifying the shader? will do . `b555b8dedce058985bfe8c544c8c46ba4821bc1a`

Ankit Meel commented

2020-03-31 10:46:27 +02:00

Original: hangs
removing the two top links, still hangs
removing color ramp from between, doesn't hang.

T74401Simplified.blend

- Original: hangs ![Screenshot 2020-03-31 at 14.11.22.png](https://archive.blender.org/developer/F8438689/Screenshot_2020-03-31_at_14.11.22.png) - removing the two top links, still hangs ![image.png](https://archive.blender.org/developer/F8438693/image.png) - removing color ramp from between, **doesn't hang**. ![image.png](https://archive.blender.org/developer/F8438688/image.png) [T74401Simplified.blend](https://archive.blender.org/developer/F8438698/T74401Simplified.blend)

Clément Foucault commented

2020-06-30 00:22:12 +02:00

Added subscriber: @Low_Polygon42

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Eevee: Crash upon expanding material preview #74401