Regression: Blender 3.4 release candidate crashes upon loading blend file #102965
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#102965
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 x64, 64GB RAM
Graphics card: RTX 8000
Blender Version
Broken: blender-3.4.0-candidate+v34.f95768d1e07b-windows.amd64-release
Worked: version: 3.4.0 Alpha, branch: master, commit date: 2022-10-10 08:50, hash:
f77eadc203
Caused by {6d7a067a83bbae7ebb965e364eb9a6b8d0f333f3}
running blender_debug_gpu.cmd produces these log files:
blender_system_info.txt
blender_debug_output.txt
Short description of error
Blender immediately crashes when attempting to load this blend file:
Exact steps for others to reproduce the error
Open Blender. Open attached blend file. warthog.blend
Added subscriber: @Eliot-Mack
Added subscriber: @iss
Can reproduce crash,
storage
was NULL at:Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @fclem
Blender 3.4 release candidate crashes upon loading blend fileto Regression: Blender 3.4 release candidate crashes upon loading blend fileAdded subscriber: @pragma37
Caused by
6d7a067a83
. To me it's just a matter of adding anullptr
check. But would like to know what @pragma37 thinks.This comment was removed by @pragma37
We could add the
nullptr
check and call it a day, but there's something weird going on.The node storage is allocated on the node init function, so it should never be null.
Even if I add the null check, the mix nodes are broken in the file:
The root cause is that
node_set_typeinfo
leaves thebNode::type
value as-is for nodes with undefined types.We may want to fix that, but given how close we are to release I guess simply checking for
node->typeinfo->type
is a much safer bet.This issue was referenced by
37b02b0432
Changed status from 'Confirmed' to: 'Resolved'
Added subscriber: @Corintio
This choice completely ruined all compatibility between 3.4 and 3.3 files in blender. Since now every material from 3.4 that we open on 3.3 is broken, with red nodes exactly how you posted here. Blender 3.4 is also not as stable as 3.3 and keeps crashing when working with rigify characters
Added subscriber: @FeAlmeida76
I have two works for big brands using Blender.
300 frames more or less, but after 10/20 frames blender close.
I try to use 3.3.2 but some material nodes are red.
Is it necessary release new versions after four moths without lot of tests? I questing me.
@Corintio @FeAlmeida76
Neither the fix for this issue nor the commit that caused it are related to your problem.
Nodes are drawn red when they have an undefined type.
By fixing the root cause I meant explicitly marking the nodes with undefined types as such, which wouldn't help with your issue at all.
If you have further comments, please keep them in #103462.