Crash when undoing a loop cut. #70752

New Issue

John Hascal · 2019-10-12T00:09:00+02:00

John Hascal commented

2019-10-12 00:09:00 +02:00

System Information
Operating system: Windows 10
Graphics card: RTX 2080

Blender Version
Broken: 2.80

Blender closes with no message when undoing a loop cut

It occurs when choosing edge loop, clicking and dragging a short distance, and then pressing the undo hotkey. A clip of it happening is shown below.
https://gyazo.com/487aec332a80855f7f1b8a7bbb14ae1d
crash_example.blend

It has often happened soon after starting a new project and doing misc actions (such as deleting half of a cube and using mirror modifier.)
However it seems more rare on a newly created cube.

**System Information** Operating system: Windows 10 Graphics card: RTX 2080 **Blender Version** Broken: 2.80 Blender closes with no message when undoing a loop cut It occurs when choosing edge loop, clicking and dragging a short distance, and then pressing the undo hotkey. A clip of it happening is shown below. https://gyazo.com/487aec332a80855f7f1b8a7bbb14ae1d [crash_example.blend](https://archive.blender.org/developer/F7807299/crash_example.blend) It has often happened soon after starting a new project and doing misc actions (such as deleting half of a cube and using mirror modifier.) However it seems more rare on a newly created cube.

John Hascal commented

2019-10-12 00:09:00 +02:00

Added subscriber: @Kyrieru

Sergey Sharybin commented

2019-10-14 14:46:15 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2019-10-14 14:46:15 +02:00

Does it happen with latest builds from builder.blender.org?
Are there any error printed to the system console (you'd need to run blender from the console) ?

Does it happen with latest builds from builder.blender.org? Are there any error printed to the system console (you'd need to run blender from the console) ?

Stanislav Blinov commented

2019-10-14 16:47:46 +02:00

Added subscriber: @Stan_Pancakes

Stanislav Blinov commented

2019-10-14 16:47:46 +02:00

@Sergey I was able to reproduce the issue with the 2.80 on Linux, but only with the active tool version of loop cut (release confirm?). With 2.81 Beta I can't reproduce regardless of tool, but here's the 2.80 crash.txt just in case:

# Blender 2.80 (sub 75), Commit date: 2019-07-29 14:47, Hash f6cb5f54494e
bpy.ops.mesh.loopcut_slide(MESH_OT_loopcut={"number_cuts":1, "smoothness":0, "falloff":'INVERSE_SQUARE', "object_index":0, "edge_index":16, "mesh_select_mode_init":(True, False, False)}, TRANSFORM_OT_edge_slide={"value":-0.182525, "single_side":False, "use_even":False, "flipped":False, "use_clamp":True, "mirror":True, "snap":False, "snap_target":'CLOSEST', "snap_point":(0, 0, 0), "snap_align":False, "snap_normal":(0, 0, 0), "correct_uv":True, "release_confirm":True, "use_accurate":False})  # Operator
bpy.ops.mesh.loopcut_slide(MESH_OT_loopcut={"number_cuts":1, "smoothness":0, "falloff":'INVERSE_SQUARE', "object_index":0, "edge_index":16, "mesh_select_mode_init":(True, False, False)}, TRANSFORM_OT_edge_slide={"value":-0.430099, "single_side":False, "use_even":False, "flipped":False, "use_clamp":True, "mirror":True, "snap":False, "snap_target":'CLOSEST', "snap_point":(0, 0, 0), "snap_align":False, "snap_normal":(0, 0, 0), "correct_uv":True, "release_confirm":True, "use_accurate":False})  # Operator

# backtrace
blender(BLI_system_backtrace+0x34) [0x561adacd1ec4]
blender(+0xc9ef65) [0x561adaaa6f65]
/usr/lib/libc.so.6(+0x3a7e0) [0x7f67f15157e0]
blender(+0x1555dd5) [0x561adb35ddd5]
blender(BKE_mesh_foreach_mapped_edge+0x79) [0x561adac7c319]
blender(mesh_foreachScreenEdge+0x10b) [0x561adb35e1db]
blender(EDBM_edge_find_nearest_ex+0x1c5) [0x561adb21d9a5]
blender(+0x15524cc) [0x561adb35a4cc]
blender(wm_gizmomap_highlight_find+0x294) [0x561adaee0974]
blender(+0x10b1851) [0x561adaeb9851]
blender(+0x10b2cec) [0x561adaebacec]
blender(wm_event_do_handlers+0x7b3) [0x561adaebb813]
blender(WM_main+0x22) [0x561adaeb0b62]
blender(main+0x344) [0x561adaa8d7d4]
/usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7f67f1501ee3]
blender(_start+0x2e) [0x561adaaa33ee]

@Sergey I was able to reproduce the issue with the 2.80 on Linux, but only with the active tool version of loop cut (release confirm?). With 2.81 Beta I can't reproduce regardless of tool, but here's the 2.80 crash.txt just in case: ``` # Blender 2.80 (sub 75), Commit date: 2019-07-29 14:47, Hash f6cb5f54494e bpy.ops.mesh.loopcut_slide(MESH_OT_loopcut={"number_cuts":1, "smoothness":0, "falloff":'INVERSE_SQUARE', "object_index":0, "edge_index":16, "mesh_select_mode_init":(True, False, False)}, TRANSFORM_OT_edge_slide={"value":-0.182525, "single_side":False, "use_even":False, "flipped":False, "use_clamp":True, "mirror":True, "snap":False, "snap_target":'CLOSEST', "snap_point":(0, 0, 0), "snap_align":False, "snap_normal":(0, 0, 0), "correct_uv":True, "release_confirm":True, "use_accurate":False}) # Operator bpy.ops.mesh.loopcut_slide(MESH_OT_loopcut={"number_cuts":1, "smoothness":0, "falloff":'INVERSE_SQUARE', "object_index":0, "edge_index":16, "mesh_select_mode_init":(True, False, False)}, TRANSFORM_OT_edge_slide={"value":-0.430099, "single_side":False, "use_even":False, "flipped":False, "use_clamp":True, "mirror":True, "snap":False, "snap_target":'CLOSEST', "snap_point":(0, 0, 0), "snap_align":False, "snap_normal":(0, 0, 0), "correct_uv":True, "release_confirm":True, "use_accurate":False}) # Operator # backtrace blender(BLI_system_backtrace+0x34) [0x561adacd1ec4] blender(+0xc9ef65) [0x561adaaa6f65] /usr/lib/libc.so.6(+0x3a7e0) [0x7f67f15157e0] blender(+0x1555dd5) [0x561adb35ddd5] blender(BKE_mesh_foreach_mapped_edge+0x79) [0x561adac7c319] blender(mesh_foreachScreenEdge+0x10b) [0x561adb35e1db] blender(EDBM_edge_find_nearest_ex+0x1c5) [0x561adb21d9a5] blender(+0x15524cc) [0x561adb35a4cc] blender(wm_gizmomap_highlight_find+0x294) [0x561adaee0974] blender(+0x10b1851) [0x561adaeb9851] blender(+0x10b2cec) [0x561adaebacec] blender(wm_event_do_handlers+0x7b3) [0x561adaebb813] blender(WM_main+0x22) [0x561adaeb0b62] blender(main+0x344) [0x561adaa8d7d4] /usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7f67f1501ee3] blender(_start+0x2e) [0x561adaaa33ee] ```

Sergey Sharybin commented

2019-10-14 16:53:51 +02:00

We can not retrospectively fix 2.80, it is done..

If the issue does not happen in 2.81 Beta and 2.82 Alpha it is most likely the issue was fixed after 2.80 release and everything is good.

We can not retrospectively fix 2.80, it is done.. If the issue does not happen in 2.81 Beta and 2.82 Alpha it is most likely the issue was fixed after 2.80 release and everything is good.

Stanislav Blinov commented

2019-10-14 17:30:57 +02:00

I know :) Log added for completeness and posterity. @Kyrieru, try the 2.81 Beta download.