Crash in BM_mesh_bm_to_me after a few simple face edit operations including bevel #104379

New Issue

Eric Cosky · 2023-02-06T15:39:31+01:00

Eric Cosky commented

2023-02-06 15:39:31 +01:00

System Information
Operating system: Windows 11
Graphics card: RTX3080

Blender Version
Broken: commit 329eeacc66 (HEAD -> master, origin/master, origin/HEAD) [Note: Crash probably has nothing to do with that commit, this is just what my local repo is currently synced to]
Worked: not sure exactly but I think it's been about a month since I last built from latest. I did not try to do these specific steps before, I was just goofing around as a post-build check of basic functionality and hit the crash.

Blender built from source after deleting the previous build folder build_windows_Full_x64_vc17_Release. No additional addins, completely stock.

Short version:
Crashes after entering face mode, doing a few extrusions, bevels and selects.

Exact steps for others to reproduce the error
Start with the default scene.

After launching either the release or debug build of Blender,
enter face edit mode,
select the single face on the default cube perpendicular to x axis,
press E, and then X, and to do a few extrusions along the X axis. Alternate with scale to shrink the face a bit.
control-b to activate bevel mode,
spin mousewheel to adjust bevel face count, and adjust the bevel depth to cross between positive and negative ranges.
maybe alt-left click to select ring of faces,
keep doing this a bit and it's crashed for me pretty consistently.
It seems to be related to the use of bevel, possibly when the faces are bevelled "backwards" in a way people probably don't usually use bevel.

In this image, it crashed after an extrusion, extrusion paired with a scale, a bevel that isn't really visible, and then another extrusion:

I was able to get it to crash in the debugger, down in BM_mesh_bm_to_me on this line:
bmesh_mesh_convert.cc:1041 need_vertsel |= BM_ELEM_CD_GET_BOOL(l, vertsel_offset);

From what I can tell, it looks like this is happening because this assignment on line 1024 sets vertsel_layer_index to -1.

  int vertsel_layer_index = CustomData_get_named_layer_index(

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: Windows 11 Graphics card: RTX3080 **Blender Version** Broken: commit 329eeacc66d13c9007e22f200304ebe902737abb (HEAD -> master, origin/master, origin/HEAD) [Note: Crash probably has nothing to do with that commit, this is just what my local repo is currently synced to] Worked: not sure exactly but I think it's been about a month since I last built from latest. I did not try to do these specific steps before, I was just goofing around as a post-build check of basic functionality and hit the crash. Blender built from source after deleting the previous build folder build_windows_Full_x64_vc17_Release. No additional addins, completely stock. Short version: Crashes after entering face mode, doing a few extrusions, bevels and selects. **Exact steps for others to reproduce the error** Start with the default scene. After launching either the release or debug build of Blender, enter face edit mode, select the single face on the default cube perpendicular to x axis, press E, and then X, and to do a few extrusions along the X axis. Alternate with scale to shrink the face a bit. control-b to activate bevel mode, spin mousewheel to adjust bevel face count, and adjust the bevel depth to cross between positive and negative ranges. maybe alt-left click to select ring of faces, keep doing this a bit and it's crashed for me pretty consistently. It seems to be related to the use of bevel, possibly when the faces are bevelled "backwards" in a way people probably don't usually use bevel. In this image, it crashed after an extrusion, extrusion paired with a scale, a bevel that isn't really visible, and then another extrusion: ![image.png](https://archive.blender.org/developer/F14252797/image.png) I was able to get it to crash in the debugger, down in BM_mesh_bm_to_me on this line: bmesh_mesh_convert.cc:1041 need_vertsel |= BM_ELEM_CD_GET_BOOL(l, vertsel_offset); From what I can tell, it looks like this is happening because this assignment on line 1024 sets vertsel_layer_index to -1. ``` int vertsel_layer_index = CustomData_get_named_layer_index( ``` ![image.png](https://archive.blender.org/developer/F14252764/image.png) **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible).

Eric Cosky commented

2023-02-06 15:39:31 +01:00

Added subscriber: @ecosky

Germano Cavalcante commented

2023-02-07 22:21:55 +01:00

I think I followed the steps correctly, but I can't replicate the crash.

Could it be that the problem has already been fixed?

Please try the latest daily build: https://builder.blender.org/download/

If the problem persists, please let us know so we can re-open the report. Don't forget to mention the specific version you tested again.

I think I followed the steps correctly, but I can't replicate the crash. ![image](/attachments/0fbb9814-166e-4eaf-8b4b-46660ade31ed) Could it be that the problem has already been fixed? Please try the latest daily build: https://builder.blender.org/download/ If the problem persists, please let us know so we can re-open the report. Don't forget to mention the specific version you tested again.

image.png

45 KiB

Germano Cavalcante added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-02-07 22:22:13 +01:00

Pratik Borhade commented

2023-02-09 19:09:45 +01:00

Hi, call stack looks identical to #104501 (also crash occurs on same line in both reports)
I guess we can consider this as duplicate.

Hi, call stack looks identical to #104501 (also crash occurs on same line in both reports) I guess we can consider this as duplicate.

Pratik Borhade added

Status

Duplicate

and removed

Status

Needs Information from User

labels 2023-02-09 19:09:55 +01:00

Pratik Borhade closed this issue

2023-02-09 19:10:05 +01:00

Eric Cosky commented

2023-02-12 06:16:47 +01:00

Thanks for checking @mano-wii . I synced to the latest ( 91346755ce ) and I am no longer able to make it crash. I may have pulled before the bug was fixed or perhaps experienced some kind of transient build issue.

Thanks for checking @mano-wii . I synced to the latest ( 91346755cefd262f5540270cfc9cd69af33d7073 ) and I am no longer able to make it crash. I may have pulled before the bug was fixed or perhaps experienced some kind of transient build issue.

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

Crash in BM_mesh_bm_to_me after a few simple face edit operations including bevel #104379