Full crash when hitting crtl+D to duplicate all the objects from a layer. #39081
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#39081
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
Windows8 Quadro 2000
Blender Version
broken: 2.70
25ad7b4
Non broken: 2.69 official release
Short description of error
In a blender file, in witch theres multiple scenes, with multiple objects some parented some not
some times if I hit "a" to select all the objects on a layer then "ctrl+d" to duplicate my selection blender
does not duplicate the objects, instead it crashes with no warning, its instantaneous dead.
Exact steps for others to reproduce the error
I have been trying to reproduce the error on a simple scene but I have not been successful, the problem
is that scenes where this has happened to me are work files meaning they are under NDA, so can't
share the files, the structure of the files is that each blender file has multiple scenes within each file,
children and parented objects and extensive use of the layers to organize each scene, I also use
grouping on the out-liner to organize the files and to be able to select things with ease.
Since I copy objects from one scene layer to the next frequently while working this crash has became my
worst nightmare, making me lose hours upon hours of work, my step are as follows.
hit "a"to select all the objects on scene on layer 1.
hit "ctrl+d" right away to duplicate all my selection
blender crashes.
Some times I select all and hit ctrl+d and blender does not
crashes so I haven't been able to figure out what combination of
variables causes this problem.
Also to work around this problem i save each time I want to duplicate all the objects form one layer
to the next, and also i found a way to counter the error, it no a solution but I might shed light as
to what part of blender the problem is located at, steps to counter as follows.
hit "a" to select all the objects on scene on layer 1
instead of hitting "ctrl+d" right way I click on one object form the scene to deselect it,
then i reselect the same object.
after this I hit "ctrl+d" to duplicate
blender duplicates all the objects and does not crashes.
I hit "m" to move the duplicated objects to the desired layer.
Let me know if you can find where this problem is located,
It's been horrible to work like this, as I'm in constant fear that
I might lose my work unexpectedly.
Thanks for your time
Changed status to: 'Open'
Added subscriber: @renderluz-2
Can you upload a file where this happens? (just use proportional edit with random - for eg to make the file unrecognizable).
Also, try running blender with command line argument
-t 1
so we can tell if this is a threading problem (this stops depsgraph from running threaded)Added subscriber: @mont29
Hi one thing on all the text above each time I write ctrl+d i mean to write shift+d you probably already figure that out but still
my brain got confused while writing.
Hi I was able to isolate the bug, now do this steps exactly as i wrote then
(i made sure I wrote the correct hot keys this time sorry about that)
this is one hard to nail bug, if you do anything else besides
the steps I wrote the bug hides and it appears as if you can duplicate
meshes with no problems, its a really sneaky problem this one.
broken: 2.70
25ad7b4
load the blender file.
just hit "a" to select all on the current visible layer, that is layer number 12.
hit "shift+d" to duplicate the selected objects.
blender should shut down immediately.
let me know if where able to replicate the behavior
bug3saved.zip.
This issue was referenced by blender/blender-addons-contrib@41dde55325
This issue was referenced by
41dde55325
Changed status from 'Open' to: 'Resolved'
Closed by commit
41dde55325
.Thanks for the report - was in fact a simple fix.
Double checked there aren't any similar oversights in the code.
Thanks for fixing it! It was a real pain working with this bug, really thanks so much for fixing it.