Blender 2.8: Crash shortly after using the "Offset edge loop cut" tool #56872
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#56872
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
Win 10 nVidia Quadro 600
Blender Version
Broken: 2.8
664865680a
Worked:
Short description of error
I'm not able to provide a .blend because as soon as I save/re-load, the problem fixes itself.
There seems to be some badness around the "Offset edge loop cut" tool as the mesh becomes corrupted after use -- leading to crashes for some operators.
Exact steps for others to reproduce the error
Go into edit mode for the default cube
Make a CTRL-R loop cut down the middle and immediately confirm
With that loop still selected: hit CTRL-SHIFT-R, drag a little, then confirm
Select entire mesh with A (notice object looks corrupted at this point)
Hit SHIFT-N to recalc normals... crash
Added subscriber: @deadpin
Added subscriber: @unblockedgamess
This comment was removed by @unblockedgamess
Added subscriber: @brecht
Added subscriber: @mont29
Cannot confirm that with current branch, might have already been fixed, can you please try again with latest build?
Ah, ok, this is a debug assert triggering which is perhaps why you didn't see the crash. Happens on latest git pull from the blender2.8 branch still.
The line in question is
in the recalc_face_normals_find_index function.
If I comment that line out, things will work. The mesh still looks broken as soon as you select-all before re-calc normals; so it seems like the assert has served a purpose I think.
Hmpf, release builds should not abort on assert… but anyway… we need to be able to reproduce that, please attach a corrupted .blend
Added subscriber: @rboxman
This comment was removed by @rboxman
Rebuilt from scratch after my previous comment to know for sure. But I can repro OP's issue when using a Debug build (compiled from source) which allows the assert to hit. I was also unsuccessful in creating a repro .blend; the act of saving and then re-loading the .blend seems to fix the issue. Perhaps the mesh loop/normal data is not being updated correctly after one of the operators but is being updated on .blend load?
I followed the same repro steps using today git. GIF here:
Still cannot reproduce with current 2.8 branch… Note that I fixed a case that could compute invalid normals for faces yesterday, so might be worth re-trying and see whether you still can reproduce now?
Yes, I can still reproduce here. My repro steps look just like the gif above from rboxman. Are you using a debug build? Is there anything I can do to help debug - like adding additional trace statements in the code path etc?
Yes am using a debug build. But you're on windows, and am on linux, since we are dealing with floats and epsilon values here, could just be a precision difference between compilers…
Here I tried reducing epsilon of
BM_face_is_normal_valid()
from1e-4
to1e-9
, still could not trigger the assert…I’d suggest you break into that function, and check values between
f->no
and computedno
. If they are very similar, then maybe epsilon is not high enough on windows for some reason. If they are totally different, then issue is somewhere else.Could be some threading stuff, starting blender from command line with
-t 1
option could be worth testing then.Alright, started with: --factory-startup -t 1
f->no == (0,0,0)
no == (0,0,1)
Many of the 18 faces of the resulting cube seem to have no face normals set:
Added subscriber: @ideasman42
Welllllll… am kind of speechless here, since I cannot reproduce that… maybe @ideasman42 will have an idea?
Can redo although this is mysterious since transform code ensures normals are updated.
Needs investigation.
This issue was referenced by
9a5df92c1b
Changed status from 'Open' to: 'Resolved'