Python API: segmentation fault on UNDO after duplicating objects from Application timer #80759
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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#80759
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: Linux-5.4.0-47-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14752 Core Profile Context 20.30
Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash:
0330d1af29
Worked: (newest version of Blender that worked as expected)
Short description of error
segmentation fault when duplicating objects using modal operator.
It doesn't happen using the legacy undo option.
Exact steps for others to reproduce the error
open the default cube scene, split the viewport ans switch to the text editor.
load the "Operator modal timer " example template.
add the following line at the end of the modal function:
bpy.ops.object.duplicate()
run the script for a very few seconds and press ESC to stop it.
press Ctrl + Z in the viewport.
segfault
blender.crash.txt
Added subscriber: @jeacom
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Confirmed'
Can confirm.
Base has a NULL object here.
Think this is very much related to #62074 (2.8: Python API: crash due to missing window context in Application timer) and #62051 (2.8: Python API: bpy.context.object not available in Application Timers) though
segmentation fault when duplicating objects using modal operator.to Python API: segmentation fault on UNDO after duplicating objects from Application timerAdded subscriber: @ideasman42
Note that I think we could even consider disabling operator execution from timers, this seems to cause a lot of bugs since operators aren't written to run outside the main event loop where the context is setup and events are being properly handled.
I'm afraid this would break so many add-ons that rely on an event timer to implement interactivity and use operators to its functionality.
also, the same issue happens for modal operators that dont have a timer, and also happens if the user triggered the operator while another modal operator is running, regardless of if it has a timer.
Checking the test file, I was under the impression this was for
bpy.app.timers
, not modal operators.Closed as duplicate of #77557
Added subscriber: @pauanyu_blender