Bmesh Crash on opening a file #49467
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
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#49467
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
Windows 10
Intel HD 4600
Blender Version
Broken: Latest Master
Worked: (optional)
Short description of error
Upon opening https://cloud.blender.org/p/gallery/57e5084f0fcf294119c5055c
you get the following backtrace with a debug build:
Exact steps for others to reproduce the error
Open https://cloud.blender.org/p/gallery/57e5084f0fcf294119c5055c
Changed status to: 'Open'
Added subscriber: @Blendify
#50400 was marked as duplicate of this issue
Added subscribers: @mont29, @Sergey
Added subscriber: @howardt
@howardt backtrace seems to point to Bevel issue?
Yes, it is triggering a "shouldn't happen" assert in Bevel. I fixed a similar problem to this recently. Will try to fix this soon.
Any news?
Added subscriber: @SteffenD
The Blenderman file is still crashing all the Buildbot builds on opening while official 2.78c can open it. Is this a regression of some sort?
All 2.8 Buildbot builds also crash.
Looking at this again now. For reference, here's a simpler file that causes the assert failure (in mesh_vert_canon): arm_simpler.blend
This issue was referenced by
8be9d68dd4
Changed status from 'Open' to: 'Resolved'
Fixed this now. Sorry for the long delay. Fixed in master; the 2.8 branch should update in a day or two when merge from 2.78 to 2.8 happens.
Thanks for taking care of this. I just compiled the very latest master and the Blenderman.blend still crashes Blender here.
Hmm. Can you see if the code you compiled includes commit
8be9d68dd4
? (git log in the blender source directory should show it).According to the build number in the splashscreen, yes.
And the bmesh_bevel.c source also contains the latest changes.
Changed status from 'Resolved' to: 'Open'
I am going to re-open this then... I can recompile later today and test as long as my render finishes.
I cannot reproduce a crash. Maybe I don't have all the same build settings. Can someone who gets a crash paste a stack backtrace? I am wondering if the crash is still in bevel, or whether it is somewhere else now.
I justed tested it again and found that my own VS2015 builds and the official Buildbot VS2015 builds crash while the VS2013 builds from the Buildbot don't.
Thanks. Do you have a stack backtrace? At any rate, I will try with VS2017 which I have at home and see what happens with that.
No, sorry, no backtrace. I'm not a coder, I'm just glad I can compile Blender myself ;)
@SteffenD to make a debug build on windows just run
make 2015 full debug
this will give a backtrace after crashing. I would test but my machine is busy rendering still.Added subscriber: @LazyDodo
for what it's worth, i can't repro on win7, with either the buildbot or my own builds....
Added subscriber: @debris
Did you also try the VS2015 builds? The VS2013 builds don't crash for me.
Yes, used a 2015/x64 buildbot from yesterday, and and build (2015/x64/debug) from master today.
After some more testing, i got the buildbot and my local release version to crash, but not my debug build... :(
I could not get it to crash with my vs2017 release or debug builds. I did try the buildbot 2015/x64/release build, and it crashed, but I don't know how to get a symbol file for this so couldn't get a meaningful stack trace. I have a strong suspicion that the problem now is not with bevel, but somewhere else.
after some convincing i had the release build put out a stracktrace
@LazyDodo, do you mind testing this patch P479: Snippet for #49467
and see if both DM are valid?
Closed as duplicate of #51540
Added subscriber: @ideasman42
Carve has known crashes and isn't maintained, one reason bmesh boolean was developed.