Cycles crash on CPU rendering , CUDA works #40963
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#40963
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
Windows 8.1 Pro 64.bit
Core i5 8gb Ram Gygabite Geforce 650 GTX 4 GB
Blender Version
Broken: Blender 2.71
5aec61f
(64bit) (buildbot sat 5) Happens in 2.71 rc2 (64bit) tooInstant crash on CPU Cycles render when opening a demo blender file from the official demo loop.
Exact steps for others to reproduce the error
Hit render and get some coffee and enjoy the crash of the titans =))
.blend file that gives this is 05_helicopter.blend in the http://download.blender.org/demo/ demoloop ( Siggraph 2013 ?!:D if it is still that demo... )
Changed status to: 'Open'
Added subscriber: @numarul7
Added subscriber: @nudelZ
can't confirm
2.71 & master works fine
OS: ubuntu 14.04
Added subscriber: @ThomasDinges
No crash on Win 7 x64,
2ec0077
with CPU.Someone with Win 8.1 64 bit ... can check ?!
Here what I get instantly http://imgur.com/UXNMmUb
Happens on 32bit build
5aec61f
and it is happening to build blender-2.71-81c3fc9-win64-vc9 , GPU CUDA render works perfectly , CPU crash.Found the problem ... in this particular blend the render threads are set to fixed 64 yet I wonder why it crash ?
Does not crash if I save that particular blend with auto-detect (4 threads) instead of default 64
Yes, the 64 threads are odd, but it still rendered fine with that here. Maybe someone on Windows 8 can reproduce the crash.
Added subscriber: @Sergey
It could be some race condition going on around, which is unleashed when using 64 threads -- this makes timing different and so.. In any case we'll need someone to reproduce the issue in order to be able to fix it..
Will check on win7 a bit later, maybe i'll be lucky :)
Added subscriber: @ChristianElsasser
i can confirm this on Win8.1 x64
when i click render right after i opened the file blender crashes after about 2 seconds
when i open the file, change the threads to auto (8 threads) it renders fine. if i change it back to 64 fixed it also renders fine. now i reopen the file, so it's fixed 64 again from the beginning -> again crashes
Blender 2.71
i7-3740QM @ 2.70GHz
GeForce GTX 660m 2gb
16GB RAM
Added subscribers: @MartijnBerger, @mont29
Martijn, maybe you could try to confirm this one? Thanks.
If two people can reproduce it, it’s no more unconfirmed really… Might be easier to reproduce with even highest number of threads maybe?
@mont29, developers still can not reproduce tho, and if we can't there's no huge chance of the issue being nailed down :(
Few questions to those who can reproduce the crash:
sergey, to answer your questions:
You can add
--debug-memory
command line argument to blender before all of the rest ones to see which blocks are no freed. This could give some hints.here's the output after adding --debug-memory
Do you mind testing latest builds from builder.blender.org? I did some threading-related fixes there today.
If it'll still crash, please try disabling "Save Buffers" in the preferences and see if it makes any difference.
ok, i did some more testing today with the versions from builder.blender.org the problem persists with blender-2.72-af92f3d-win64 and win64_cmake_vc2013
i couldn't find a save buffers in the preferences? if you meant the checkbox in the performance section of the rendersettings: that didn't make a difference
funny enough, the gooseberry branch seems to lock up blender too (no hover states for buttons for example) but as long as i don't click anywhere it seems to render in the background and then after it finished starts responding again. showing me the finished rendering. when not changing any settings and just hitting F12 again it renders perfectly smooth without locking up.
Yes, i was referencing to the "Save Buffers" from the Performance panel of the render settings.
I didn't get "lock up blender too". Original report was about crash, not about locking?
With "Save Buffers" deselected I get only locking but it renders fine.
Without "Save Buffers" I get more aggressive locking of the whole pc but no crash.
I guess this one can be marked fixed based on build
0c5eb88
I have tested now.:) Happy programmering guys!
Changed status from 'Open' to: 'Resolved'
Locking might be caused by much more intense memory usage.
But as long crash doesn't happen anymore, would consider the issue fixed. Please let us know if it strikes you back.
Added subscriber: @lehuan5062
Hello, I'm trying to render this file: https://drive.google.com/file/d/1km5gSrqeWuA8ldsR1Xy8esdk-uZ631aV/view?usp=sharing
Blender crashes everytime I hit F12 in Cycles CPU mode.
It's fine with EEVEE and Cycles GPU.
System: CPU i5 9400f, 16GB Ram, 2060 6GB.
Blender version: 2.90.1