Crash with Fluid Simulation with EEVEE Motion Blur #80386

New Issue

Floatharr · 2020-09-02T17:31:26+02:00

Floatharr commented

2020-09-02 17:31:26 +02:00

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

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29

Short description of error
Blender crashes if I try to render a fluid simulation with EEVEE motion blur with more than 1 step.

excerpt from blender.crash.txt blender.crash.txt :

bpy.context.scene.eevee.use_motion_blur = True  # Property
bpy.context.scene.eevee.motion_blur_steps = 2  # Property

# backtrace
Exception Record:

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


Stack trace:
nvoglv64.dll        :0x00007FF952227B80  DrvPresentBuffers
nvoglv64.dll        :0x00007FF95210E5FC  Symbols not available

Exact steps for others to reproduce the error
With factory default:

Add fluid to default cube
Change Type to Flow
Change Flow Type to Liquid
Duplicate default cube, scale it up
Change Type to Domain
Change Domain Type to Liquid
Enable Delete In Obstacle
Enable Mesh
Hit spacebar to simulate a bit
Enable EEVEE Motion Blur
Change Motion Blur Steps to 2 or more
Render frame, crash.

Simple blend file based on factory default where you can hit space to simulate a few frames and then render to crash:
fluidmotioncrash.blend

See attached video:
Q2YeFVtgcx.mp4

blender_system_info.txt
blender_debug_output.txt

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06 **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `0330d1af29` **Short description of error** Blender crashes if I try to render a fluid simulation with EEVEE motion blur with more than 1 step. excerpt from blender.crash.txt [blender.crash.txt](https://archive.blender.org/developer/F8853354/blender.crash.txt) : ``` bpy.context.scene.eevee.use_motion_blur = True # Property bpy.context.scene.eevee.motion_blur_steps = 2 # Property # backtrace Exception Record: ExceptionCode : EXCEPTION_ACCESS_VIOLATION Exception Address : 0x00007FF952365540 Exception Module : nvoglv64.dll Exception Flags : 0x00000000 Exception Parameters : 0x2 Parameters[0] : 0x0000000000000000 Parameters[1] : 0xFFFFFFFFFFFFFFFF Stack trace: nvoglv64.dll :0x00007FF952227B80 DrvPresentBuffers nvoglv64.dll :0x00007FF95210E5FC Symbols not available ``` **Exact steps for others to reproduce the error** With factory default: 1. Add fluid to default cube 2. Change Type to Flow 3. Change Flow Type to Liquid 4. Duplicate default cube, scale it up 5. Change Type to Domain 6. Change Domain Type to Liquid 7. Enable Delete In Obstacle 8. Enable Mesh 9. Hit spacebar to simulate a bit 10. Enable EEVEE Motion Blur 11. Change Motion Blur Steps to 2 or more 12. Render frame, crash. Simple blend file based on factory default where you can hit space to simulate a few frames and then render to crash: [fluidmotioncrash.blend](https://archive.blender.org/developer/F8833487/fluidmotioncrash.blend) See attached video: [Q2YeFVtgcx.mp4](https://archive.blender.org/developer/F8833470/Q2YeFVtgcx.mp4) [blender_system_info.txt](https://archive.blender.org/developer/F8853352/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8853351/blender_debug_output.txt)

Floatharr commented

2020-09-02 17:31:26 +02:00

Added subscriber: @Floatharr

Richard Antalik commented

2020-09-08 04:24:17 +02:00

Added subscriber: @iss

Richard Antalik commented

2020-09-08 04:24:17 +02:00

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

Richard Antalik commented

2020-09-08 04:24:17 +02:00

Can't reproduce this.

I get crash when opening your file, that is unrelated issue though.

Please download development build from https://builder.blender.org/download/
Run blender with blender_debug_log.cmd and upload files created after crash

Can't reproduce this. I get crash when opening your file, that is unrelated issue though. Please download development build from https://builder.blender.org/download/ Run blender with `blender_debug_log.cmd` and upload files created after crash

Floatharr commented

2020-09-08 09:07:48 +02:00

Here are the files generated on the latest 2.91 development build
blender_debug_output.txt
blender_system_info.txt

blender_debug_output.txt also references another file not in the generated folder, I thought it might be useful to include:

blender.crash.txt

Here are the files generated on the latest 2.91 development build [blender_debug_output.txt](https://archive.blender.org/developer/F8853351/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8853352/blender_system_info.txt) blender_debug_output.txt also references another file not in the generated folder, I thought it might be useful to include: [blender.crash.txt](https://archive.blender.org/developer/F8853354/blender.crash.txt)

Richard Antalik commented

2020-09-09 01:16:40 +02:00

In #80386#1011417, @Floatharr wrote:
blender_debug_output.txt also references another file not in the generated folder, I thought it might be useful to include:

Thanks I would have requested this one if I find it was generated.

From crash file it looks like crash happened in GPU driver. Can you update to latest version and re-check?

> In #80386#1011417, @Floatharr wrote: > blender_debug_output.txt also references another file not in the generated folder, I thought it might be useful to include: Thanks I would have requested this one if I find it was generated. From crash file it looks like crash happened in GPU driver. Can you update to latest version and re-check?

Floatharr commented

2020-09-09 15:20:03 +02:00

I am using Driver version 452.06 which as of August 17th is the latest version available. There is no newer driver to update to.

Richard Antalik commented

2020-09-10 23:59:28 +02:00

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

Richard Antalik commented

2020-09-10 23:59:28 +02:00

Added subscriber: @lichtwerk

Richard Antalik commented

2020-09-10 23:59:28 +02:00

Thanks for info. @lichtwerk can you try to reproduce crash here?

Philipp Oeser commented

2020-11-04 17:29:27 +01:00

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

Philipp Oeser commented

2020-11-04 17:29:27 +01:00

Sorry, also cannot reproduce this.

Crash seems to be in NVidia Drivers nvoglv64.dll
Could we give this one more try in a fresh build from https://builder.blender.org/download/ and once again with updated drivers?

Thx in advance!

Sorry, also cannot reproduce this. Crash seems to be in NVidia Drivers `nvoglv64.dll` Could we give this one more try in a fresh build from https://builder.blender.org/download/ and once again with updated drivers? Thx in advance!

Floatharr commented

2020-11-04 18:48:50 +01:00

I can still reproduce the crash with latest drivers (version 467.09) in 2.92 alpha and 2.91 beta with both the included file and following steps in the video.

I did notice that I called Motion Blur Steps "samples" where in the interface they're called "steps", and the text instructions are missing the step where I scale up the domain. There might have been confusion between EEVEE render samples and motion blur steps. I have corrected the description.

Just for the sake of completeness I tried a bunch of random things: disabled second screen, primary screen from 144 to 60 hz, disabled second GPU, changed every setting in nvidia control panel in the blender.exe profile, disabled gsync, quit every background task, and a bunch of random settings changes in blender preferences, disabled windows game mode, game bar, and hardware-accelerated GPU scheduling. No change, still crashing.

I can still reproduce the crash with latest drivers (version 467.09) in 2.92 alpha and 2.91 beta with both the included file and following steps in the video. I did notice that I called Motion Blur Steps "samples" where in the interface they're called "steps", and the text instructions are missing the step where I scale up the domain. There might have been confusion between EEVEE render samples and motion blur steps. I have corrected the description. Just for the sake of completeness I tried a bunch of random things: disabled second screen, primary screen from 144 to 60 hz, disabled second GPU, changed every setting in nvidia control panel in the blender.exe profile, disabled gsync, quit every background task, and a bunch of random settings changes in blender preferences, disabled windows game mode, game bar, and hardware-accelerated GPU scheduling. No change, still crashing.

Philipp Oeser commented

2020-11-04 18:54:07 +01:00

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

Floatharr commented

2020-11-04 19:53:57 +01:00

0005-0040.mp4

Since others have failed to reproduce, I felt like it's best I do some investigation on my own. Hopefully this helps to narrow it down.

By setting the max blur distance of the motion blur to 0 px I was able to render a frame. I tried a few settings and was able to render this animation with 2 pixel distance and 3 steps. It appears as if the fluid is rapidly rushing to the center in every frame in the motion blur.

Tinkering with the Max Blur and Steps makes it feel like every combination of settings that renders more than 1 frame in the past or future(?) crashes. Setting shutter to 0 or max pixels to 0, or steps to 1 fixes the crash, every other setting is broken. I have crashed the software maybe 100+ times in the last hour. My non-programmer guess is that whatever is fetching/storing data about the shape of the fluid in the past or the future is giving a bunch of junk/zeroes/NaN which is causing a crash.

[0005-0040.mp4](https://archive.blender.org/developer/F9198580/0005-0040.mp4) Since others have failed to reproduce, I felt like it's best I do some investigation on my own. Hopefully this helps to narrow it down. By setting the max blur distance of the motion blur to 0 px I was able to render a frame. I tried a few settings and was able to render this animation with 2 pixel distance and 3 steps. It appears as if the fluid is rapidly rushing to the center in every frame in the motion blur. Tinkering with the Max Blur and Steps makes it feel like every combination of settings that renders more than 1 frame in the past or future(?) crashes. Setting shutter to 0 or max pixels to 0, or steps to 1 fixes the crash, every other setting is broken. I have crashed the software maybe 100+ times in the last hour. My non-programmer guess is that whatever is fetching/storing data about the shape of the fluid in the past or the future is giving a bunch of junk/zeroes/NaN which is causing a crash.

Floatharr commented

2020-11-04 20:07:55 +01:00

fluidmotioncrashanimation.blend

I have managed to get the file I was tinkering with to a state where it renders consistently but with incorrect/broken motion blur. With 64 render samples, 499 px max blur, and 63 steps I believe this frame should have smooth motion blur on it. Maybe this'll help with debugging.

![brokenmotionblur.png](https://archive.blender.org/developer/F9198977/brokenmotionblur.png) [fluidmotioncrashanimation.blend](https://archive.blender.org/developer/F9198981/fluidmotioncrashanimation.blend) I have managed to get the file I was tinkering with to a state where it renders consistently but with incorrect/broken motion blur. With 64 render samples, 499 px max blur, and 63 steps I believe this frame should have smooth motion blur on it. Maybe this'll help with debugging.

YAFU commented

2020-11-04 20:12:26 +01:00

Added subscriber: @YAFU

YAFU commented

2020-11-04 20:12:26 +01:00

I cannot reproduce the problem (crashes) here on Linux, GTX 960 (455.28). Blender 2.92 Alpha (master)

Have you tried installing the latest nvidia drivers with the "clean install" option enabled?

I cannot reproduce the problem (crashes) here on Linux, GTX 960 (455.28). Blender 2.92 Alpha (master) Have you tried installing the latest nvidia drivers with the "clean install" option enabled?

Floatharr commented

2020-11-05 09:18:11 +01:00

Nuking my drivers would be counterproductive to resolving the bug, no way to know what caused it if it works. Everything else is working flawlessly, and I don't work with fluid sims regularly so I prefer to be able to reproduce the bug.

Pratik Borhade commented

2021-06-09 18:21:51 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-06-09 18:21:51 +02:00

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

Pratik Borhade commented

2021-06-09 18:21:51 +02:00

Stack trace:
nvoglv64.dll :0x00007FF952227B80 DrvPresentBuffers
nvoglv64.dll :0x00007FF95210E5FC Symbols not available

looked at crash.text, may be related to #85977 (NVidia: Random crashes in 'DrvPresentBuffers')

Can you check again with recent blender builds? (https://builder.blender.org/download/daily/)

>Stack trace: >nvoglv64.dll :0x00007FF952227B80 DrvPresentBuffers >nvoglv64.dll :0x00007FF95210E5FC Symbols not available looked at `crash.text`, may be related to #85977 (NVidia: Random crashes in 'DrvPresentBuffers') Can you check again with recent blender builds? (https://builder.blender.org/download/daily/)

Floatharr commented

2021-06-09 20:41:22 +02:00

I can't reproduce either in 2.93 stable or the latest 3.0 alpha by following the steps or using the attached file. I also tested the file with 2.91.2 which I still had installed, and I can crash it reliably. Feels like this one is fixed.

Pratik Borhade commented

2021-06-10 06:00:29 +02:00

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

Pratik Borhade closed this issue

2021-06-10 06:00:29 +02:00

Pratik Borhade self-assigned this 2021-06-10 06:00:29 +02:00

Pratik Borhade commented

2021-06-10 06:00:29 +02:00

I can't reproduce either in 2.93 stable or the latest 3.0 alpha... Feels like this one is fixed.

Ok, marking this as resolved then. Feel free to reopen or create a new bug report if problem reappears.

Thanks again for the report :)

>I can't reproduce either in 2.93 stable or the latest 3.0 alpha... Feels like this one is fixed. Ok, marking this as resolved then. Feel free to reopen or create a new bug report if problem reappears. Thanks again for the report :)

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

Crash with Fluid Simulation with EEVEE Motion Blur #80386