Crash on Python console autocompletion #32692
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#32692
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?
%%%Crash sometimes occurs when using Python console autocompletion. I did not managed to find exact reproduction scenarios, crashes occur spontaneously. Hope fault location will help:
blender[3648] general protection ip:1070205 sp:7fffdae10930 error:0 in blender[400000+3a26000]
System info file and loaded model file attached.%%%
Changed status to: 'Open'
%%%This is not enough info to redo the crash.
You need to give steps to redo the crash, even if it happens only one in 10 times, the steps you go through to get the crash to happen are really important.
marking as incomplete.%%%
%%%i can confirm (random?) crashes on auto-complete, but not provide any steps to reproduce it either.
IIRC, it happened for me when auto-completing variable attributes, and the variable was a ref to blender data, like:
var = bpy.context.object
do stuff here
var.<strg+spacebar> CRASH
the problem might have to do with a context, that changes over time, and accessing attributes might try to read from invalid memory address - but it's just a wild guess%%%
%%%This is likely invalid memory access: see
http://www.blender.org/documentation/blender_python_api_2_63_release/info_gotcha.html#edit-mode-memory-access
there is a cmake build time option that checks for this but slows down blender/python execution too. - WITH_PYTHON_SAFETY
closing. can re-open if you find steps to redo which are not accessing freed data (which is known limitation)%%%
Changed status from 'Open' to: 'Archived'
%%%pretty sure it's invalid memory access:
Edit mode:
bpy.data.meshes['Cube'].polygons[0]
Object mode
bpy.data.meshes['Cube'].polygons[-292049]
auto-completing p does crash blender, as the reference is bad. So we just need to be careful with vars which refer to geometry and have been assigned in edit mode.%%%
Added subscriber: @demarcog83
Try this solution
https://developer.blender.org/T43491