Cycles crash at the end of the render #95025
Labels
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#95025
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: windows 11
Graphics card: GTX 1070 ti
Blender Version
Broken: 3.0
Worked: 2.93.7
Short description of error
Almost always, when I render, missing few samples to finish the cycles crashes. Usually when 4 to 6 samples are missing from the end.
Exact steps for others to reproduce the error
The crash is random and I can't reproduce the exact steps. All I know is that the crash only happens a few steps before denoising.
I don't know if it may be some configuration that I have to do in windows because of the video card.
I look forward to some help. Thanks
Added subscriber: @Leejunfan
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Needs User Info'
Please download latest alpha build from https://builder.blender.org/download/daily/ and check if issue persists. To provide more info run file
blender_debug_log.cmd
and after crash upload created files.Hello, I did the debug test in Blender 3.0 and I had the crash. Follow the files.
progressiva 3d.crash.txt
blender_system_info.txt
blender_debug_output.txt
I got a file that doesn't render, it crashes at 121 samples, I tested it on 3.0 and 3.1 and the crash is on both. On 2.93 it works fine.progressiva 3d_bug.blend
Added subscriber: @Wovchick
There was crash file created
C:\Users\conta\AppData\Local\Temp\progressiva 3d.crash.txt
, please upload it here as well.Does this happen when you run file
blender_factory_startup.cmd
? I was able to render image without any issues.I tried again here and it still didn't work.
progressiva 3d.crash.txt
blender_system_info.txt
blender_debug_output.txt
Changed status from 'Needs User Info' to: 'Needs Triage'
Thanks for checking, Crash file did not contain any useful information really. Also I see your GPU drivers are relatively recent, but perhaps updating these may resolve this issue. It would help to also check if this issue happens with certain renderer settings only like denoising for example.
Unfortunately I don't think I would be able to reproduce this issue and don't see other developers with similar system configuration I could ask.
I'll test some options here and get in touch if it solves.
What is the best driver for my 1070 to work well in Blender? Game Ready or Studio Ready?
I am not aware if either is preferred, both should work. Not sure exactly how these work in Nvidia. I think in AMD studio drivers or equivalent to that were basically older game ready drivers with some tweaks perhaps. I would reffer to what manufacturer says about what the difference is and recommendation.
Added subscriber: @Garek
To note, debug output says that it rendered 128 samples, it seems like it crashes while denoising. You can disable it to make sure it's that.
Additionally try to use latest 3.1.0 since it got fix for a similar problem
f179637222
https://builder.blender.org/download/daily/
And also you can use OptiX since as far as I see it you used OIDN to denoise.
Added subscriber: @mano-wii
Changed status from 'Needs Triage' to: 'Needs User Info'
Thanks for the report. Unfortunately the scenario described is too time consuming for us to track down, we require the bug reporter to narrow down the problem.
Rendering 121 (or 128) frames with the possibility of not replicating the problem doesn't seem like a good use of time.
While this is a real issue, it is only happening to a few people so far and it is not clear whether it's a solvable problem from Blender side...
So if you can simplify the file even further and figure out which setting is causing the crash, that would be appreciated.
I followed these guidelines here and it looks like the issue is resolved in 3.1
Changed status from 'Needs User Info' to: 'Resolved'
Good to know the issue is resolved.
If the problem persists, please let us know so we can re-open the report.
Don't forget to mention the specific version you tested again.