Crash while rendering short evee animation to ffmpeg video. #57560
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#57560
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 10 1609 Build NVidia 1050 Ti OC 4Gb
Blender Version
Broken: blender-2.80.0-git.ae87adc73a2-windows64
Short description of error
Doing some Animation and setting Tests with the evee engine. Finaly I was trying to do a short video out of it. Near finish of the animation rendering in Evee, Blender simply just Closed completly.
animationTest.blend
Exact steps for others to reproduce the error
See upper description.
Added subscriber: @Zyankali
Added subscribers: @Sergey, @lichtwerk
Can confirm here.
Ran the render twice, assert happened on different frames.
Ran the render again with the
--threads 1
commandline option and didnt have issues.So seems to be a threading conflict / race condition?
@Sergey : does that ring a bell? Could you take over?
unknown complete unwilling close of Blender while rendeing short evee animation to ffmpeg video.to Crash while rendering short evee animation to ffmpeg video.Changed status from 'Open' to: 'Resolved'
Can no longer reproduce the error and there were fixes related on a race condition of synchronizing data back to original object (this is what the backtrace suggests crash is happening in).
Let us know if the issue still happens for you. For until then considering the issue resolved.
Error still there. standby.blend
Logo.blend with blender
168d3fd528
Changed status from 'Resolved' to: 'Open'
using the single thread mode of blender solves the problem blender chrashing while creating a ffmpeg video.
Please always provide exact steps reproducing the error. It also better idea to submit a new bug report rather than re-opening existing ones. You can reference the older report from a new one, and then if it's needed those can be merged together.
Helps a lot keeping things under testable control.
I've tried opening every file form this report, changing the output path to something what exists on my system, hitting Ctrl-F12. Did not see any crashes so far.
So, is it some step which i am missing? Or is it just some tricky threading thing which are always tricky to reproduce on a different configuration of CPU?
One of the files is actually set to PNG output btw.
So questions:
Ok i´ll start a new thread/bug report than with added details and results of fourther tests.
Cool. Include as many details as possible, every detail matters!
One more thing you can do, is to run from a command line and see whether there are any errors/warnings printed there.
P.S. We hate bugs probably even more than you, but we are powerless if we can not reproduce the issue :(
Changed status from 'Open' to: 'Archived'