Trying to render on the GPU with tiles larger than a few hundred makes Blender crash #70336
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#70336
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-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30
Blender Version
Broken: version: 2.81 (sub 12), branch: master (modified), commit date: 2019-09-27 17:16, hash:
be985bdde2
Short description of error
I have had this issue since I started using 2.8x back in December. I've been trying to follow the Cycles optimisation tips by the Blender Guru in this video , but when I try to set the render tiles to 512 or 1024 with the GPU selected, Blender has consistently been crashing every time, especially right at the end of a completed render of some reason. Also, rendering on the CPU does not cause these crashes for me strangely.
Exact steps for others to reproduce the error
Set the render tiles to one of those numbers on a scene. I don't know what is causing the issue, but if it is a universal problem, Blender should crash eventually from rendering with those settings.
Added subscriber: @Frozen_Death_Knight
Added subscriber: @StephenSwaney
/me guesses randomly: perhaps you are blowing out the GPU memory. Can you show us the error message? Also a .blend would be useful
Optimal tile size depends on your card. Maybe do a bit of testing to find appropriate size
@StephenSwaney That's the thing, Blender rendering rarely works out properly and I have been trying out different settings for a long time. I've tried everything from 100 up to 1k and it rarely works out the way I expect it to. Here's another example of an error I get fairly often, a CUDA error:
Added subscriber: @LazyDodo
I'm gonna guess it's a TDR issue, too much work is queued and the OS kills the GPU driver after it gets unresponsive for more than a few seconds.
@LazyDodo Okay. Anything that can be done on my end to avoid those issues?
I'd probably start by validating it is a TDR issue, by looking in the event viewer from around the time of the crash and see if there are any TDR events reported.
Added subscriber: @brecht
It is not recommended anymore to use such large tile sizes, and smaller ones often render faster now. When using denoising or many render passes in general, large tile sizes will also run out of memory.
In any case we require a .blend file and exact steps to reproduce problem, this bug report is too vague.
@brecht Okay, I will keep that in mind.
Here is is a file I am currently working on which crashes for me every time I press render. Since I don't know what setting is causing the crash, this is all I can really give you. I am using a Geforce GTX 980 card and quite recently installed the latest drivers.
Old Bird.blend
Added subscriber: @iss
Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'
@Frozen_Death_Knight Is this still an issue with latest build? https://builder.blender.org/download/
Added subscriber: @lichtwerk
Changed status from 'Needs User Info' to: 'Archived'
Will close since we did not hear back and this is most probably an issue with large tile sizes and denoising [which are not only slow, but eat a lot of (v)RAM].
This is a documented limitation:
https://docs.blender.org/manual/en/dev/render/layers/denoising.html#notes-and-issues
(I can render the file on GPU with a small tilesize -- but have to go down one multires level as well due to my poor 970m)
Thx for the report anyways, feel free to comment again if issues persist...