Page MenuHome

EEVEE crash when keyframing integer properties on modifiers with motion blur enabled
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits, Windows-10-10.0.19041.630-SP0 64 Bits
Graphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38, GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35

Blender Version
Broken: version: Bisecting points to rB879ed5a165ae: EEVEE: Motion Blur: Fix issue with batch overflowing with VBOs
Worked: Before rB879ed5a165ae870c7a8967fdd0f084ea7b16ca13

Short description of error
While rendering with Eevee's motion blur enabled, a crash occurs when an integer property on a modifier is keyframed so that a step occurs a fraction of a frame later.

Exact steps for others to reproduce the error

NOTE: Heisenbug: It doesn’t appear when using a debug build.

Create a cube and attach an Array modifier to it.
Add keyframes to the Count property so that it is 1 on frame 1, and 5 on frame 39. This should result in the count value transitioning from 2 to 3 on frame 15.25 in the graph editor.
Attempt to render frame 14-16 with motion blur enabled by pressing Ctrl-F12. A crash should result.

Following the same steps with the Screw modifier's Iterations property results in the same crash, so it's not just an Array problem.

Workaround
Using Sample Keyframes on the animation curve prevents crashing, but obviously isn't ideal if the curve needs to be edited later.

This is my first time reporting a bug, so I hope this makes sense. Thanks for reading!

Event Timeline

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Sep 30 2020, 6:24 PM

I can not reproduce crash. Does this happen when you click on File > Defaults > Load Factory Settings?

Run Blender with blender_debug_log.cmd and upload created files after crash.

Yes, it happens with default factory settings. However, I dug out my laptop and copied over the same build, and things seem to work fine on there. I've attached the debug files for both.

Desktop (crashed)

Laptop (didn't crash)

Richard Antalik (ISS) changed the task status from Needs Information from User to Needs Triage.Oct 1 2020, 1:38 PM

from desktop_blender.crash.txt file it looks like crash in GPU driver. So please update drivers if possible.

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Needs Information from User.Oct 27 2020, 10:39 AM

Also cannot reproduce this.

@Tim Johansen (timjvtx): did you have any luck upgrading drivers?
Could you also check if this is still a problem in a fresh build from https://builder.blender.org/download/?

Sorry for not following up sooner. I'm currently running the latest Nvidia studio driver (version 456.71, 10/20/2020), and the crash still happens on today's build of 2.91. The only difference is that the debug log doesn't show the error anymore (pasted below). I was able to reproduce the crash on another PC that also has an RTX 2060, so maybe it's a quirk of that specific card. Probably not worth worrying about if that's the case.

I1027 15:30:28.558326 4776 blender_python.cpp:194] Debug flags initialized to:
CPU flags:

AVX2       : True
AVX        : True
SSE4.1     : True
SSE3       : True
SSE2       : True
BVH layout : EMBREE
Split      : False

CUDA flags:

Adaptive Compile : False

OptiX flags:

CUDA streams : 1

OpenCL flags:

Device type    : ALL
Debug          : False
Memory limit   : 0

I1027 15:30:28.619345 4776 device_opencl.cpp:48] CLEW initialization succeeded.
I1027 15:30:28.637349 4776 device_cuda.cpp:41] CUEW initialization succeeded
I1027 15:30:28.637349 4776 device_cuda.cpp:43] Found precompiled kernels

Richard Antalik (ISS) closed this task as Archived.Nov 14 2020, 5:47 AM
Richard Antalik (ISS) claimed this task.

This really seems to be GPU related bug, and it may be resolved in future driver versions.
Unfortunately nvidia doesn't have bugtracker so this may take long time to be fixed.

So I will close this report. Thanks for reporting though.

Windows 10
GTX 1070 & GTX 1060
Blender 2.92.0

Latest drivers (457.30 Studio)

I have the same crash issue with animated array integer and enabled motion blur in EEVEE.

# Blender 2.92.0, Commit date: 2020-11-22 18:21, Hash 7bab87c119f4

# backtrace
Exception Record:

ExceptionCode         : EXCEPTION_ACCESS_VIOLATION
Exception Address     : 0x00007FF9D0F4CA84
Exception Module      : nvoglv64.dll
Exception Flags       : 0x00000000
Exception Parameters  : 0x2
	Parameters[0] : 0x0000000000000000
	Parameters[1] : 0x0000000000000000


Stack trace:
nvoglv64.dll        :0x00007FF9D0D37B80  DrvPresentBuffers
nvoglv64.dll        :0x00007FF9D0C0D5C8  Symbols not available
Evan Wilson (EAW) reopened this task as Confirmed.Dec 4 2020, 3:31 AM
Evan Wilson (EAW) triaged this task as High priority.

The crash started happening sometime between the Blender 2.90 2020-07-12 build and the full 2.90 release.

Thank you @Tim Johansen (timjvtx) for that information, it was quite helpful at narrowing down the responsible commit.

@Clément Foucault (fclem) bisecting points to rB879ed5a165ae: EEVEE: Motion Blur: Fix issue with batch overflowing with VBOs. As @Philipp Oeser (lichtwerk) and @Richard Antalik (ISS) are not able to reproduce, I am guessing this is a NVIDIA on Windows only issue, affecting drivers from 391.35 to 457.30, aka every Blender supported NVIDIA GPU.

Following T82808's lead, I'll set the preliminary priority to High, and tag 2.92.

Evan Wilson (EAW) renamed this task from Eevee crash when keyframing integer properties on modifiers with motion blur enabled to EEVEE crash when keyframing integer properties on modifiers with motion blur enabled.Dec 4 2020, 3:42 AM
Evan Wilson (EAW) removed Richard Antalik (ISS) as the assignee of this task.
Evan Wilson (EAW) updated the task description. (Show Details)

Just noticed @Chris Bell (ChrisKK) has a ATI Radeon RX580, so it doesn't look like it is just NVIDIA cards.
@Chris Bell (ChrisKK) what driver do are you using?

I tested the file from T82808 at the same time as this one and T83371. While the same commit is responsible for crashing on my machine, T82808's file is too complex, with no keyframed arrays that I can see, for me to comfortably merge the reports.

Just noticed @Chris Bell (ChrisKK) has a ATI Radeon RX580, so it doesn't look like it is just NVIDIA cards.
@Chris Bell (ChrisKK) what driver do are you using?

I'm using the stable release of Adrenalin 2020, version 20.9.1