Blender 3.4 & 3.5 Cycles crashes constantly after rendering +-10 animation frames -- MacOS 13 & 13.0.1 Ventura -- #102453
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#102453
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: macOS-13.0.1-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.48
Blender Version
Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-11-11 21:32, hash:
03ccf37162
Worked: ??
Short description of error
Rendering this simple scene as an animation crashes, no matter what.!?
I reduced the scene and settings to almost zero + factory settings, but it's still crashing.
When letting it run in the viewport it works fine. Still renders work fine, even on the original file with hefty settings etc.
It is rendering on cycles experimental GPU. (only CPU or both, Metal, experimental or not are not working either) Always same result.
Exact steps for others to reproduce the error
Open the scene file below and hit render animation. For my mac setup it crashes/instantly quits mostly before frame 10. (no crash logs created)
I tested it with blender 3.4 and 3.5. - with factory settings
I tried out everything like OS-restart, only blender working on the system etc. After almost 7 hours I gave up.
When started blender via Terminal, after the immediate crash, terminal exits without the chance to capture something.
Withe the original file on hefty settings, it won't start rendering one sample, it crashes straight away.
Only thing I can think of is that there is some V-memory issue. When I watch my memory and the memory of blender it's OK. Blender uses up to 380MB.
What I can't see in blender on macOS is the VRAM, it's not displayed in the Statusbar.
OS memory 64GB / 16GB GPU memory
sample.blend
xcode 14.01
Added subscriber: @Nurb2Kea
Added subscriber: @iss
On first attempt rendering hung at 17 frames, but on subsequent attempts I was able to render without any issues.
Operating system: macOS-12.6-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.101
will re-check after OS update
Added subscriber: @shugo
I've got the same issue on 3.4/3.5 (Windows 11, RTX4090). Sometimes I can finish rendering animation and sometimes it gets stucked.
Even after OS update, I am not able to reproduce.
Still continuing with : Version: 3.5.0 Alpha, branch: master, commit date: 2022-12-08 23:10, hash:
f898190362
After 20 frames the fun is over.
So I'm basically not able to render any animation at the moment !
(I updated to xcode 14.1 and it's commandline tools, updated brew to the latest, deleted the build_darwin & cycles cache AND compiled successfully )
Settings: See above initial post
station ani.blend
@Nurb2Kea do yo test this with your own builds? If so I would recommend to check with official build. It should be exactly same, but just in case there is some issue with your builds.
Already did that with the same result!
With this new file I was able to reproduce hangup. Seems to happen only sometimes, but reproduction rate is good.
Will try tu pull some information why this happens
There are many problems with cycles in 3.5.
Rendered 3DView in two windows crashes MacOS etc.
You can look at those reports as well to see if they are related !?
https://developer.blender.org/T102799
https://developer.blender.org/T102866
https://developer.blender.org/T102696
and lately I noticed this :
Changed status from 'Needs Triage' to: 'Confirmed'
Don't think I get much more info here, with debugger code got stuck on exception in
MetalKernelPipeline::compile()
on printf "Error getting function cycles_metal_integrator_init_from_bake"Not sure if this is fatal and whether it is related to freeze, but will confirm at least.
Closed as duplicate of #103327
Added subscriber: @QBer
With Radeon Pro Vega 56 8 GB, Render window appears blank reporting a problem with Metal buffer capacity while working with only one no complex object that has some bumps applied to textures.
Back to 3.3.2 working quite well now after the last update as bump problems on Eevee seems resolved.
Added subscriber: @FeAlmeida76
Same here in windows, after 10/20 frames Blender close using OptiX or CUDA
I Updated my rtx 3060 driver, but nothing changes
Blender 3.4.1
Added subscriber: @Vano
I have the same issue i have rtx 2070
Running with a NVidia RTX card, I've got this working again with OptiX and Denoise enabled.
(Speaking for NVidia users only)
BLUF: The issue is related to the recent NVidia GeForce Game Ready Drivers, including the most recent v528.49 from 02/08/2023. Switching to the NVidia Studio Driver v528.49 from 02/08/2023 fixed the issue.
Symptom: Blender 3.4.1 crashing when entering rendered viewport mode.
Replication steps:
Preferences > System > OptiX > NVidia video card
Render Properties >
Render Engine > Cycles
Feature Set > Experimental
Device > GPU Compute
Sampling >
Viewport >
Denoise >
Denoiser > OptiX
Render >
Denoise >
Denoiser > OptiX
Switch to Viewport Shading or attempt to Render.
With the Game Ready Driver installed, turning off the Denoise option works, while OptiX is selected under the System Preferences. Additionally, with Denoise enabled, the Game Ready Driver works with Viewport > Automatic or OpenImageDenoise selected or Render > OpenImageDenoise selected. Switching to Viewport Shading or Rendering while OptiX is selected in the applicable position, causes Blender to crash when the NVidia Game Ready Driver is installed. Switching to the Studio Driver prevents this issue from occurring at this time.
Solution: Use NVidia Studio Driver when using Blender.
Here's a screenshot of it working as of 02/21/2023.
Hope this helps! Good luck!
3.4.1 and Beta 3.5 Crashing when changing to shading viewport, still working perfect in 3.3
No matter how simple or complex files are.
I also found that Beta 3.5 was working fine for a while and then and with no reason begins crashing when F12 is pushed even with the files that worked fine before, making it not usable at all in my machine.
By the way, Beta 3.5 viewport textures look weird when Viewport Metal is used
ImacPro
3,2 Ghz Xeon W 8 Cores
Radeon Pro Vega 56 8Gb
32 Gb 2666 Mhz DDR4
Ventura 13.2.1
Report included
see here and 4 of the above comments:
#103327
@Nurb2Kea I see you reopened also #103327, but this report was merged there. Do you have reason to believe this is different issue though?
No, I think they are related and still present.
Thanks for info. So I am closing as duplicate of #103327 again.