When Bevel modifier is applied to specific mesh Blender crashes #50064

New Issue

Chaz Fried · 2016-11-17T19:56:15+01:00

Chaz Fried commented

2016-11-17 19:56:15 +01:00

System Information
Windows 7 professional 64-bit
Processor:
Intel Core 2 duo CPU p8400@2.26GHz
RAM: 2GB
Graphics: Mobile Intel 4 Series Express Chipset Family (apologies if not correct, will correct if need be)

Blender Version
Broken: 2.77 abf6f08

A previously applied bevel modifier was added to a .blend, and made invisible. After editing and joining 2 meshes, array modifier was tested, and worked wonderfully. Bevel modifier was made visible and cause blender to crash immediately.

Exact steps for others to reproduce the errorGears; (time 5_53).blend

Open .blend
Make bevel modifier visible
Crash

or

Remove bevel modifier
reapply bevel
Blender crashes

**System Information** Windows 7 professional 64-bit Processor: Intel Core 2 duo CPU p8400@2.26GHz RAM: 2GB Graphics: Mobile Intel 4 Series Express Chipset Family (apologies if not correct, will correct if need be) **Blender Version** Broken: 2.77 abf6f08 A previously applied bevel modifier was added to a .blend, and made invisible. After editing and joining 2 meshes, array modifier was tested, and worked wonderfully. Bevel modifier was made visible and cause blender to crash immediately. **Exact steps for others to reproduce the error**[Gears; (time 5_53).blend](https://archive.blender.org/developer/F402743/Gears___time_5_53_.blend) 1. Open .blend 2. Make bevel modifier visible 3. Crash or 1. Remove bevel modifier 2. reapply bevel 3. Blender crashes

Chaz Fried commented

2016-11-17 19:56:15 +01:00

Changed status to: 'Open'

Chaz Fried commented

2016-11-17 19:56:15 +01:00

Added subscriber: @PhantomModeler

Sergey Sharybin commented

2016-11-18 10:43:41 +01:00

Added subscribers: @howardt, @Sergey

Howard Trickey was assigned by Sergey Sharybin

2016-11-18 10:43:41 +01:00

Sergey Sharybin commented

2016-11-18 10:43:41 +01:00

Can reproduce crash with latest master.

@howardt, mind having a look here? :) Thanks!

Can reproduce crash with latest master. @howardt, mind having a look here? :) Thanks!

Howard Trickey commented

2016-11-18 17:26:35 +01:00

Hope to get to this soon.

Howard Trickey commented

2016-12-08 13:55:45 +01:00

Looking at this now. It seems that the mesh in the test file violates the assumed invariants about BMeshes. If you start blender with --debug, and then toggle into Edit mode, the validation code reports that a particular face has a duplicate vertex and a duplicate edge.

I will try to make bevel not crash when this happens, but curious if you (PhantomModeler) remember how you made this mesh, as we should try to figure out which editing tool created this mess. (By the way, even without the integrity problem, there also some vertices that are extremely close together that you probably intended to merge. I'm guessing that perhaps Knife was used and it didn't snap to a vertex, but instead to an edge near the intended vertex.)

Looking at this now. It seems that the mesh in the test file violates the assumed invariants about BMeshes. If you start blender with --debug, and then toggle into Edit mode, the validation code reports that a particular face has a duplicate vertex and a duplicate edge. I will try to make bevel not crash when this happens, but curious if you (PhantomModeler) remember how you made this mesh, as we should try to figure out which editing tool created this mess. (By the way, even without the integrity problem, there also some vertices that are extremely close together that you probably intended to merge. I'm guessing that perhaps Knife was used and it didn't snap to a vertex, but instead to an edge near the intended vertex.)

Howard Trickey commented

2016-12-14 14:32:09 +01:00

Changed status from 'Open' to: 'Resolved'

Howard Trickey closed this issue

2016-12-14 14:32:09 +01:00

Howard Trickey commented

2016-12-14 14:32:09 +01:00

We write our tools under the assumption that the meshes are 'valid'. (If you run the python command mesh.validate(True) it can tell you whether the mesh is valid or not. Rather than try to put all sorts of protective code in all the tools, our policy is to instead make sure no tools produce invalid meshes. At any rate, even if Blender didn't crash, most tools could produce crap results on invalid meshes. Clearly some tool has produced your corrupt mesh -- in the example .blend file that you uploaded -- but without help understanding how that mesh was produced, I'm afraid there's nothing more than can be done here.
Closing this bug, but feel free to open a new bug or reopen this if you can reproduce the mesh corruption (that is, can provide an uncorrupted model and instructions for a next step that causes corruption).
Thanks anyway for the report.

We write our tools under the assumption that the meshes are 'valid'. (If you run the python command mesh.validate(True) it can tell you whether the mesh is valid or not. Rather than try to put all sorts of protective code in all the tools, our policy is to instead make sure no tools produce invalid meshes. At any rate, even if Blender didn't crash, most tools could produce crap results on invalid meshes. Clearly some tool has produced your corrupt mesh -- in the example .blend file that you uploaded -- but without help understanding how that mesh was produced, I'm afraid there's nothing more than can be done here. Closing this bug, but feel free to open a new bug or reopen this if you can reproduce the mesh corruption (that is, can provide an uncorrupted model and instructions for a next step that causes corruption). Thanks anyway for the report.

Matthias Thurau commented

2017-05-24 23:04:39 +02:00

Added subscriber: @Zweistein

Matthias Thurau commented

2017-05-24 23:04:39 +02:00

Cant you simply add that test "mesh.validate(True)" before you add the modifier? Blender keeps crashing and my work is not saved. This is really annoying as that crash happens all the time. Im using boolean to create my meshes.

Campbell Barton commented

2017-05-25 12:50:13 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2017-05-25 12:50:13 +02:00

Validate is too slow, it needs to be done for any operation that might generate bad data.

It seems there is a bug in the gears add-on. Will check on making it validate all its output.

Validate is too slow, it needs to be done for any operation that might generate bad data. It seems there is a bug in the gears add-on. Will check on making it validate all its output.

Campbell Barton commented

2017-05-25 12:50:23 +02:00

Changed status from 'Resolved' to: 'Archived'

Howard Trickey commented

2017-05-25 12:56:58 +02:00

Hi Matthias,

We'd rather have the buggy tools that create invalid meshes call validate() afterwards (this fixes most of the problems), rather than have every tool in blender call validate() before running. In case of original report here, Gears is known to be buggy. Carve boolean is also known to be buggy -- is that the one you are using?

Hi Matthias, We'd rather have the buggy tools that create invalid meshes call validate() afterwards (this fixes most of the problems), rather than have every tool in blender call validate() before running. In case of original report here, Gears is known to be buggy. Carve boolean is also known to be buggy -- is that the one you are using?

Campbell Barton commented

2017-05-25 14:30:59 +02:00

Note if you can re-create the cause of a corrupt mesh, this is worth reporting as a separate bug.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

When Bevel modifier is applied to specific mesh Blender crashes #50064