Bizarre bug that Blender will crash if I move the timeline without render current frame first #115647
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#115647
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 11
Graphics card: RTX4090
Blender Version
Broken: 3.5, 3.6, 4.0.
Worked: ---.
Short description of error
This problem is not that serious since I have found the solution, but it still concerns me why this happens. All versions of Blender I've used from 3.5 to 4.0.1 have this bug.
The bug is in some of my projects, if I open it without rendering the current frame in the first, every attempt to move the timeline will cause the crash including importing something that will force the timeline to frame 0, but if I render the current frame, and it doesn't need to be finished, as long as anything shows loaded in the right corner of the rendering window, this bug is gone, I can do freely to the timeline now.
I am not sure what exactly causes it, and my projects are all quite big to upload. Is the crash report file going to show something?
Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
Hi, thanks for report. Please, provide example file to let us to reproduce this crash. Make sure add-ons is disabled and drivers of pc is up to date.
Is there any other way? the smallest project that has this bug is around 4GB and contains my designs that can't be released yet
Well, in this case there is no way to fix this. Could you reimplements project from default cube to reproduce this? Or maybe delete all unrelated content from copy of project to reduce size and make it possible to share it? High size project will be rejected to be simplified in any way, even if bug can be confirmed. Developers shouldn't deep in gigabyte-projects of any users.
I have isolated the problem collection in the project, delete it will also solved the problem. And I tested if I packed all files inside and the bug is still there.
But when I copied this isolated project to my mac and run the same procedure nothing happends.
https://drive.google.com/file/d/1Sod7V2-XTlCcTqfz9g0n_y4tKQdiJa45/view?usp=sharing
have you tried the project I uploaded
Checked on the file, no crash here though
Couple of questions:
Yes, I deleted some vertex of the face. And that project is the simplest I can get to recreate the bug.
One more thing I think might help is that all projects with this bug are all using collections appended from other projects of mine since they shared some set objects, and the bug project I have uploaded is also appended from the original one and then packed.
Hi, unable to confirm either in 4.1. Could it be due to animated visibility properties? Can you share system info and also verify the crash with factory settings?
Help > Save System Info
File > Defaults > Load Factory Settings
the factory setting fixed the crash somehow, can you find which setting or addon causes the crash in the crash report I posted?
and the factory setting seems to stop the rigify UI script by default
Good to know. Could you share system info:
Help > Save System
. Possiblywiggle_bones
add-on if you've it installed/enabled.Yes, I have that addon enabled
Thanks. Previously wiggle_bones caused the crash on moving playback when visibility properties are animated.
You can just disable that add-on to verify the culprit.
OK, thank you so much for this
Think we can close this now (assuming wiggle_bones is the culprit).