Crash during rendering of animation #81183
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#81183
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-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06
Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-24 19:43, hash:
0106e17f07
Worked: (newest version of Blender that worked as expected)
Short description of error
Crashes during rendering of animation every time. The frame number is random. OIDN comp node memory leak?
ctrl + f12 to test.
blender_system_info.txt
blender_debug_output.txt
balls.blend
balls.crash.txt
!!Triaging Note:!! Both the
balls
and thesphere's compositing
stack traces are identical (except memory location of course).While this report doesn't involve 2 scenes like T84438 and T84324, it does have 2 layers.
Added subscriber: @3di
Crash during renderingto Crash during rendering of animationJust tried again with the latest Nvidia Driver:
blender_system_info.txt
blender_debug_output.txt
balls.crash.txt
Added subscriber: @EAW
Hi @3di, thanks for the report. I am looking to see if this is tied into some other recent reports, which is the reason for the note below.
!!Triaging Note:!! Another GeForce GTX 1070 and Driver version 45X.XX crash, but this stack trace doesn't match the others as OIDN isn't checked on in the viewport. However, there are OIDN nodes in the compositor.
Just checked and I was able to render all the way through with the OIDN comp nodes muted.
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Confirmed'
Can confirm, Crash occured on frame 3, not sure if this is random though,
Exception thrown: read access violation. tex_ was nullptr
anyone looking at this? Blender hard crashing with no log during animations again today.
This time it created a log. I've tried running today's daily build at factory defaults and the same issue is happening. Tried to render this animation 5 times now and it's crashing each time. Maybe this should be escalated? Seems quite severe not being able to render animations.
blender_debug_output.txt
blender_system_info.txt
spheres compositing.crash.txt
I think it might be something to do with the file saving, because in my scene I have a file output node in the compositor which is writing a multilayer exr (only 3 layers), and the main output settings are writing out a jpg sequence. I just tried changing the jpg sequence to a ffmpeg video, and it was able to make it to 146 out of 300 frames, whereas when it was set to jpg sequence it was crashing every time within the first 50 frames.
Can't share the file (already shared one anyway), but basically it's a particle system scattering objects over a displaced plane, a cube with principled volume bsdf, sun and spotlight, two view layers so I can render the volume and spheres seperately. In the compositor it then has 4 denoise nodes which denoise the glossy direct, glossy indirect, volume direct, volume indirect, adds them appropriately and then saves to a multilayer full float the denoised combined and multipled glossy passes, the denoised and combined volume passes, and the undenoised combined volume passes.
OK scrap that. I've just sat and watched it closely to see at what stage it crashes. It saves files fine, then it crashes halfway through rendering the first view layer of the next frame. So it's nothing to do with denoising or file saving.
hmm, i've just noticed something else. The first time this file crashed, even though auto save was set to every 2 mins, there was no auto saves for around about 1 hour prior to the crash. So possibly it's auto save related?
This comment was removed by @3di
Added subscriber: @Jeroen-Bakker
I am not able to reproduce this after
7a005fb7d1
. @3di can you check with a latest build tomorrow?No longer crashing. Great work, thanks.
Changed status from 'Confirmed' to: 'Resolved'
Just saw that this was still open.
Closing as resolved.