Box Trim Causes Crash #83078
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#83078
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: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30
Blender Version
Broken: version: 2.91.0, branch: master, commit date: 2020-11-25 08:34, hash:
0f45cab862
Worked: (newest version of Blender that worked as expected)
Short description of error
The Box/Lasso Trim tool in sculpt mode causes the program to crash. Task manager shows 99% CPU usage. This happens even if I restore factory settings.
Exact steps for others to reproduce the error
Added subscriber: @mike.cairns86
Added subscriber: @Foaly
Changed status from 'Needs Triage' to: 'Needs User Info'
I cannot confirm.
Does this only happen with high poly meshes? In that case you might be running out of memory.
Please run
blender_debug_log.cmd
from the Blender folder, reproduce the crash, and then upload the log files here.Added subscriber: @lichtwerk
It is kinda slow.
With the default sphere in the sculpting template, it takes multiple seconds here to box trim half of it.
Hi Philipp, thanks for looking into this. After giving it some time, the Box/Trim tool does it's job, but it does seem to take longer than it should. What concerns me is the fact that Task Manager shows Blender using up to 99% of the CPU while calculating. However, if I give it a minute it becomes resolved.
Thanks,
Mike
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Added subscriber: @PabloDobarro
Afaik, this is using exact booleans under the hood [which can be slow], so I assume this is more or less expected behavior @PabloDobarro ?
Work on improving performance will continue, potential performance improvements are not handled as bug reports though.
Will leave up final decision to @PabloDobarro
Thank you!
Added subscriber: @iss
I have created report for this just now, haven't noticed this one. I think I have better steps to reproduce so I will merge this one.
Closed as duplicate of #83504
I'd like to note that this bug was not about it actually crashing, but about it being very slow.
So this is not the same as the bug it was merged with.
However, I think that's just how it is, and boolean performance improvements will come in the future.
Ah I did not read whole discussion here. Yes in general performance issues are rarely bugs unless they are regression. And exact boolean is unfortunately slow.
Closed as duplicate of #84229