Blender crashes frequently when rendering Smoke Simulation (Manta Flow) with Cycles using GPU #102491

Closed
opened 2022-11-14 03:57:08 +01:00 by Facundo · 11 comments

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86
system-info.txt
Splash.jpg
Captura de pantalla 2022-11-13 234509.jpg

Blender Version
Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-10-03 00:19, hash: d4d40f3b69
Worked: (newest version of Blender that worked as expected)

Short description of error
Blender crashes frequently when rendering Smoke Simulation (Manta Flow) with Cycles using GPU, when configured with either CUDA or OptiX, having checked both the CPU (Ryzen 7 3700X) and GPU (Nvidia GeForce RTX 3080). It looks like it only crashes when both checkboxes are activated.

Exact steps for others to reproduce the error

  • Make a Smoke simulation using Manta Flow. It doesn't need to be a complex simulation, just any simulation
  • Change the render engine to cycles
  • Configure it to use either CUDA or OptiX, and enable both checkboxes to use CPU and GPU.
  • Render (nearly 90% of the times it crashes after some progress on the render).

I think this strongly depends on the Hardware I'm using.

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86 [system-info.txt](https://archive.blender.org/developer/F13908934/system-info.txt) ![Splash.jpg](https://archive.blender.org/developer/F13908935/Splash.jpg) ![Captura de pantalla 2022-11-13 234509.jpg](https://archive.blender.org/developer/F13909049/Captura_de_pantalla_2022-11-13_234509.jpg) **Blender Version** Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-10-03 00:19, hash: `d4d40f3b69` Worked: (newest version of Blender that worked as expected) **Short description of error** Blender crashes frequently when rendering Smoke Simulation (Manta Flow) with Cycles using GPU, when configured with either CUDA or OptiX, having checked both the CPU (Ryzen 7 3700X) and GPU (Nvidia GeForce RTX 3080). It looks like it only crashes when both checkboxes are activated. **Exact steps for others to reproduce the error** - Make a Smoke simulation using Manta Flow. It doesn't need to be a complex simulation, just any simulation - Change the render engine to cycles - Configure it to use either CUDA or OptiX, and enable both checkboxes to use CPU and GPU. - Render (nearly 90% of the times it crashes after some progress on the render). I think this strongly depends on the Hardware I'm using.
Author

Added subscriber: @Facu

Added subscriber: @Facu
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

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

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

Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-10-03 00:19, hash: d4d40f3b69

Hi, thanks for the report. Please check again in newer development build: https://builder.blender.org/download/daily/
I tried to redo it locally with Quick Liquid but didn't get the crash

I think this strongly depends on the Hardware I'm using.

Crash may not be hardware specific. Please also upload crash logs:
Open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).2019_12_04_upload_icon_developer_blender_org.png


Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78```
> Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-10-03 00:19, hash: d4d40f3b69 Hi, thanks for the report. Please check again in newer development build: https://builder.blender.org/download/daily/ I tried to redo it locally with `Quick Liquid` but didn't get the crash > I think this strongly depends on the Hardware I'm using. Crash may not be hardware specific. Please also upload crash logs: Open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer).![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png) - - - ```**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78```
Author

blender_debug_output.txt

blender_system_info.txt

I tried it on the latest version of 3.5.0 Alpha and had to try a few times in order to reproduce it. I did reproduce it when I increased a little the Resolution of the Smoke Simulation. Here are the two logs files as requested. Regarding the other crash.txt file, I din't find it in the Temp directory.

Please let me know if you need anything else.

[blender_debug_output.txt](https://archive.blender.org/developer/F13919247/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F13919244/blender_system_info.txt) I tried it on the latest version of 3.5.0 Alpha and had to try a few times in order to reproduce it. I did reproduce it when I increased a little the Resolution of the Smoke Simulation. Here are the two logs files as requested. Regarding the other crash.txt file, I din't find it in the Temp directory. Please let me know if you need anything else.
Member

hi, thanks for the information. Does this happen in particular blend/volume file? say Grinder16.blend in this case? Could you attach it?
Perhaps crash happens due to high memory usage? Can you observe hardware utilization and memory usage at the time of crash?
I could not find any information associated with crash in log file.

hi, thanks for the information. Does this happen in particular blend/volume file? say `Grinder16.blend` in this case? Could you attach it? Perhaps crash happens due to high memory usage? Can you observe hardware utilization and memory usage at the time of crash? I could not find any information associated with crash in log file.
Author

Hi, I'm not sure if this only happens in a partular blend/volume file. I'm sorry but I can't provide this file, is for a client. I will check the memory usage and the hardware utilization, and try to reproduce it in a new file. I'll let you know when I find out something.

Hi, I'm not sure if this only happens in a partular blend/volume file. I'm sorry but I can't provide this file, is for a client. I will check the memory usage and the hardware utilization, and try to reproduce it in a new file. I'll let you know when I find out something.
Member

Hi, any updates?

Hi, any updates?

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

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

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

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
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
3 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#102491
No description provided.