Crash when opening the Compositor in an old file #117795
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#117795
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.23
Blender Version
Broken: version: 4.1.0 Alpha, branch: main, commit date: 2024-02-02 22:23, hash:
f355b2026216
Worked: Blender 2.83.20 LTS
Short description of error
When working on a really old file (started in 2.59, saved in 2.64), I noticed that opening the compositor would crash constantly.
I've deleted everything in the scene, all datablocks, all viewlayers, all workspaces, but there's no way I can open the compositor not even in a completely empty scene.
Crashes in 4.0, and previous too.
The only way I managed to make it work, is by removing all compositing nodes via Python, but even then after I can enter the Compositor, switching to the Options tab makes it crash again.
Exact steps for others to reproduce the error
compositor_crash_report.blend
file.It's not a huge deal if it's not possible to fix, but I'm just curious where it crashes since I've deleted everything already.
Can confirm,
override_owner_id->override_library
was null.@mont29 This seems to be crashing somewhere in the override system. These null pointer checks make it open, but not sure if there is a deeper problem.
That is... very old indeed :|
I guess the liboverrides come from the conversion of the proxies here. But will need deeper investigation to understand what is actually happening am afraid. there should never be null liboverride data pointer in such case afaik.
@pablovazquez the file you attached seems to have been saved with Blender 4.0... Mind attaching the original files?
I suspect we have a doversion issue on the
ID.flag
itself here (it makes absolutely no sense for the compositing nodetree of the scene to have itsembedded liboverride
flag set).actually... I think I know what is the issue: versioning code clearing all non-persistent flags in IDs (for 2.76.5 blendfile version)... did not cover embedded IDs!
This comes from when the only
ID.flag
data was split in persistent flags, and runtime tags, in3fcf535d2e
.Note that we can easily fix the conversion of older files. But I don't think we can do anything about files converted and saved again by more recent versions of Blender having this bug.
@pablovazquez PR !118921 should in theory fix the issue when opening the 2.64 file.
I cannot imagine a way to solve the cases like your 2.4 file reliably (though we could for sure address this specific case with some post-reading validation checks).
Bastien Montagne referenced this issue2024-03-01 11:32:33 +01:00
I wasn't around at the time but I've got plenty of old files (saved in the original version) so I can keep an eye if I find similar crashes.
Thanks for the fix and research! There's nothing like going through old files and opening it in a modern Blender.