Blender crashes when separating mesh #72593

New Issue

Andrew Price · 2019-12-20T03:23:14+01:00

Andrew Price commented

2019-12-20 03:23:14 +01:00

System Information
Operating system: Win 10 64bit
Graphics card: 2x Titan GTX

Blender Version
Broken: 2.81a
Worked: unsure

Short description of error
In attached blend, separating mesh (P > Selected) crashes blender.

Exact steps for others to reproduce the error

Open this attached blend file: andaz corridor2.blend
When you open, one edge will be selected. Press P>Separate.
Blender will crash, giving this reason in the cmd prompt:

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF7B00617CB
Module : C:\Program Files\Blender Foundation\Blender 2.81\blender.exe

**System Information** Operating system: Win 10 64bit Graphics card: 2x Titan GTX **Blender Version** Broken: 2.81a Worked: unsure **Short description of error** In attached blend, separating mesh (P > Selected) crashes blender. **Exact steps for others to reproduce the error** - Open this attached blend file: [andaz corridor2.blend](https://archive.blender.org/developer/F8235771/andaz_corridor2.blend) - When you open, one edge will be selected. Press P>Separate. - Blender will crash, giving this reason in the cmd prompt: Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF7B00617CB Module : C:\Program Files\Blender Foundation\Blender 2.81\blender.exe

Andrew Price commented

2019-12-20 03:23:14 +01:00

Added subscriber: @AndrewPrice

Clément Foucault was assigned by Campbell Barton

2019-12-20 03:54:12 +01:00

Campbell Barton commented

2019-12-20 03:55:34 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2019-12-20 03:55:34 +01:00

This raises assert: DRW_mesh_batch_cache_get_surface_shaded(), at 'gpumat_array_len <= cache->mat_len'

Seems to be caused by the new mesh not using it's materials.

This raises assert: `DRW_mesh_batch_cache_get_surface_shaded(), at 'gpumat_array_len <= cache->mat_len'` Seems to be caused by the new mesh not using it's materials.

Clément Foucault commented

2020-01-13 18:30:00 +01:00

@ideasman42 I'm not sure what to expect. It seems like the boolean modifier is what set the material number to 0 in the Mesh. So is it a problem with the drawing code expecting Mesh->totcol to be equal to Ob->totcol or a problem in the boolean modifier?

Campbell Barton commented

2020-01-21 18:35:20 +01:00

Checking on this, older blender releases (2.7x for eg) didn't have the requirement that these numbers matched, so it could be fixed in viewport drawing code.

OTOH, not many modifiers copy geometry between objects, so we could make this a requirement for the modifier stack.

Checking on this, older blender releases (2.7x for eg) didn't have the requirement that these numbers matched, so it could be fixed in viewport drawing code. OTOH, not many modifiers copy geometry between objects, so we could make this a requirement for the modifier stack.

Clément Foucault was unassigned by Campbell Barton

2020-01-27 04:50:32 +01:00

Campbell Barton self-assigned this 2020-01-27 04:50:32 +01:00

Campbell Barton commented

2020-01-27 04:50:32 +01:00

Added subscriber: @fclem

Campbell Barton commented

2020-01-27 04:50:32 +01:00

While it's arguable the drawing code should support this, it's less trouble to ensure all modifiers output meshes with the same number of materials, claiming this task.

While it's arguable the drawing code *should* support this, it's less trouble to ensure all modifiers output meshes with the same number of materials, claiming this task.

Clément Foucault commented

2020-01-28 14:13:57 +01:00

OTOH, I can easily patch the drawing code. @ideasman42 Choose whatever you think is the best option.

Campbell Barton commented

2020-01-28 15:19:26 +01:00

@fclem, if the fix is straightforward and not likely to cause issues, that'd be good.

Campbell Barton was unassigned by Clément Foucault

2020-01-28 15:55:43 +01:00

Clément Foucault self-assigned this 2020-01-28 15:55:43 +01:00

blender-admin commented

2020-01-28 16:39:33 +01:00

This issue was referenced by 3fd4c88e3a

This issue was referenced by 3fd4c88e3a2e9d99d45a0856fcc339e013c0a79a

Clément Foucault commented

2020-01-28 16:39:56 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Clément Foucault closed this issue

2020-01-28 16:39:56 +01:00

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

Blender crashes when separating mesh #72593