Page MenuHome

Boolean in carve solver can crash blender when doing Difference operation
Closed, ResolvedPublic

Description

System Information
win 10 , gtx 1070
Blender Version
2.78.1 3e460b6

Worked:
2.77, (in general all versions before the bmesh solver was added back.- before mesh just disappeared, now it is hard crash.)

Short description of error

Boolean modifier in carve mode can crash blender{F378024} when applied or moved in modifier stack. I am adding file with easy to replicated solution. But this is happening randomly also on closed mesh and in general on more complex ones.

Exact steps for others to reproduce the error
in the file apply only boolean modifier or move it to the top of the stack (in carve mode, bmesh works just fine)

file

Event Timeline

Bastien Montagne (mont29) lowered the priority of this task from 90 to 50.

Asan reports shows crash happening in Bevel code, @Howard Trickey (howardt) mind having a look? thanks.

I suspect this might be similar or the same as the problem in T49467, which I haven't had time to fix yet. I should have time to look at this soon - not next week, but the week after.

@Howard Trickey (howardt) I've been looking at the bevel code, and found that just before the crash, the BMILoop l has a null BMIEdge, so l->v, l->f are fine, but l->e is NULL.

See the file: source/blender/bmesh/tools/bmesh_bevel.c:3854 where I noticed the error.

Howard Trickey (howardt) changed the task status from Unknown Status to Resolved.Nov 29 2016, 1:43 PM

I confirm that this happened in the version of blender cited (commit 3e460b6), but at the latest revision of 2.78 (bd5ae46c) the crash does not happen. I am closing this one. Feel free to reopen if the crash still happens for you. There is another bevel crash bug task that I am going to look at now, so I am not discounting that there may be a bug to fix here. Going to look at that other task now.