Blender Crash with custom gizmo (EXCEPTION_ACCESS_VIOLATION, no python backtrace) #109111
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#109111
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-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98
Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash:
e1ccd9d4a1d3
Worked: None
Short description of error
Using one specific custom gizmo will crash when spliting 3d view area, with no python backtrace crash log camerahelper.crash.txt
Exact steps for others to reproduce the error
Hello, thanks for the report, but I'm not sure if we should disassemble the addon. Please report the bug to the author of the addon, or simplify it to a single file with as small a size as possible.
Yeah, I am the author of this addon. I tested it for a while to find what code crash the blender. I just create a one-file-version addon to show this error @mod_moder
Steps:
Can confirm the crash with updated file.
using
self.gizmos.clear()
instead of removing each one by separate removes the crash, don't know if it works for youexecuting the script already gives a heap-use-after-free in debug builds:
seems like we are calling
GizmoGroup_gizmo_remove
and then still accessing stuff that was removedAh, I wasnt refreshing the browser tab here, lets try what @guishe suggested, @1029910278 : does this work for you?
yes it works.Seems this error happended when delete gizmos in for loop.
I have lots of gizmos for different usages in one gizmo group. Should it be separate them into different groups to prevent this error?
The problem was using
self._rotate_gz.clear()
, couldn't say exactly why (i think it tries to freethe memory of the gizmos objects, but they are already cleaned onself.gizmos.remove(gizmo)
), but using inteadself._rotate_gz = dict()
solves the issue. You can use also arrays, butarray.clear()
will make same issues thatdict.clear()
does.See video
got it. Already fix the problem.Thanks! :)