Crash making a node group with a frame #95395

Closed
opened 2022-02-01 14:58:24 +01:00 by Lukas Tönne · 12 comments
Member

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-26 21:12, hash: 0e86c60c28
Worked: (newest version of Blender that worked as expected)

Apparently caused by dd01ce2cd0

Short description of error
Crash when making a node group with a frame node and unselected nodes inside the frame.

Exact steps for others to reproduce the error

  1. Make a simple node tree with one node (does not have to be functional or connected to the output)
  2. Wrap the node in a frame (ctrl+J)
  3. Select only the frame node, the inside node should be unselected.image.png
  4. Make a node group (ctrl+G)
    The crash seems to happen if there are any unselected nodes within the frame:
  • If there are multiple nodes in the frame it crashes if one of them is not selected.
  • If all nodes inside the frame are selected it works as expected.
  • If the frame is empty it works as expected.
    make_group_crash.blend
**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-26 21:12, hash: `0e86c60c28` Worked: (newest version of Blender that worked as expected) Apparently caused by dd01ce2cd0 **Short description of error** Crash when making a node group with a frame node and unselected nodes inside the frame. **Exact steps for others to reproduce the error** 1. Make a simple node tree with one node (does not have to be functional or connected to the output) 1. Wrap the node in a frame (ctrl+J) 1. Select **only** the frame node, the inside node should be unselected.![image.png](https://archive.blender.org/developer/F12839268/image.png) 1. Make a node group (ctrl+G) The crash seems to happen if there are *any* unselected nodes within the frame: * If there are multiple nodes in the frame it crashes if one of them is not selected. * If all nodes inside the frame are selected it works as expected. * If the frame is empty it works as expected. [make_group_crash.blend](https://archive.blender.org/developer/F12839267/make_group_crash.blend)
Author
Member

Added subscriber: @LukasTonne

Added subscriber: @LukasTonne
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Can confirm, will check.

Can confirm, will check.
Member

Apparently caused by dd01ce2cd0

Apparently caused by dd01ce2cd0
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Marking as High priority since it is a crash regression (even though maybe not the most likely one to run into).

CC @JacquesLucke

Marking as High priority since it is a crash regression (even though maybe not the most likely one to run into). CC @JacquesLucke
Author
Member

even though maybe not the most likely one to run into

I use frames a lot as a method for commenting in nodes, and then i turn them into actual node groups when the frame gets too big and unwieldy. So it happens quite a lot when i want to exclude some of the nodes in the frame. I've learned to avoid it, but i don't think it's particularly unlikely for people making complex node systems.

> even though maybe not the most likely one to run into I use frames a lot as a method for commenting in nodes, and then i turn them into actual node groups when the frame gets too big and unwieldy. So it happens quite a lot when i want to exclude some of the nodes in the frame. I've learned to avoid it, but i don't think it's particularly unlikely for people making complex node systems.
Member

In #95395#1299345, @LukasTonne wrote:

even though maybe not the most likely one to run into

I use frames a lot as a method for commenting in nodes, and then i turn them into actual node groups when the frame gets too big and unwieldy. So it happens quite a lot when i want to exclude some of the nodes in the frame. I've learned to avoid it, but i don't think it's particularly unlikely for people making complex node systems.

Sorry, yeah this was not meant to make this less severe, hope this will get fixed due to High prio soonish.
P.S.: you might be interested in D13737

> In #95395#1299345, @LukasTonne wrote: >> even though maybe not the most likely one to run into > > I use frames a lot as a method for commenting in nodes, and then i turn them into actual node groups when the frame gets too big and unwieldy. So it happens quite a lot when i want to exclude some of the nodes in the frame. I've learned to avoid it, but i don't think it's particularly unlikely for people making complex node systems. Sorry, yeah this was not meant to make this less severe, hope this will get fixed due to High prio soonish. P.S.: you might be interested in [D13737](https://archive.blender.org/developer/D13737)
Jacques Lucke self-assigned this 2022-02-01 16:41:45 +01:00
Author
Member

In #95395#1299348, @lichtwerk wrote:

In #95395#1299345, @LukasTonne wrote:

even though maybe not the most likely one to run into

I use frames a lot as a method for commenting in nodes, and then i turn them into actual node groups when the frame gets too big and unwieldy. So it happens quite a lot when i want to exclude some of the nodes in the frame. I've learned to avoid it, but i don't think it's particularly unlikely for people making complex node systems.

Sorry, yeah this was not meant to make this less severe, hope this will get fixed due to High prio soonish.
P.S.: you might be interested in D13737

Thanks! I just wanted to add some context. The new select behavior looks good, much more usable.

> In #95395#1299348, @lichtwerk wrote: >> In #95395#1299345, @LukasTonne wrote: >>> even though maybe not the most likely one to run into >> >> I use frames a lot as a method for commenting in nodes, and then i turn them into actual node groups when the frame gets too big and unwieldy. So it happens quite a lot when i want to exclude some of the nodes in the frame. I've learned to avoid it, but i don't think it's particularly unlikely for people making complex node systems. > > Sorry, yeah this was not meant to make this less severe, hope this will get fixed due to High prio soonish. > P.S.: you might be interested in [D13737](https://archive.blender.org/developer/D13737) Thanks! I just wanted to add some context. The new select behavior looks good, much more usable.

This issue was referenced by 2bd71b49e7

This issue was referenced by 2bd71b49e79325863bfe3c561fa03653231c9914
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#95395
No description provided.