Edit mesh for shape key ,change tool option menu values cause crash #61904

New Issue

takeshi funahashi · 2019-02-24T07:58:28+01:00

takeshi funahashi commented

2019-02-24 07:58:28 +01:00

version: 2.80 (sub 44), branch: master, commit date: 2019-02-13 00:09, hash: ba6cf3cdb6, type:
build date: 2019/02/13, 12:56 platform: Windows
OpenGL:
renderer: 'GeForce GTX 980 Ti/PCIe/SSE2'
vendor: 'NVIDIA Corporation'
version: '4.5.0 NVIDIA 417.71'

Move vertex to edit "shape key" , and use "option menu" to change transform value cause blender crash.

But it do not happen, when I edit "base shape" .

Exact steps for others to reproduce the error
1 open this blend file (as simple as possible).
shapekey_propotionaledit.blend

2 move current active vertex (edit) with move (rotate, transform, scale) tool .

3 Open pop up option menu, and try to change x, y, z value of option menu. it cause crash.

4 Same crash happen about "roate , move, scale" tool, when edit property values of each tool option.

5 If I remove shape keys, change values cause no issue.

version: 2.80 (sub 44), branch: master, commit date: 2019-02-13 00:09, hash: ba6cf3cdb649, type: build date: 2019/02/13, 12:56 platform: Windows OpenGL: renderer: 'GeForce GTX 980 Ti/PCIe/SSE2' vendor: 'NVIDIA Corporation' version: '4.5.0 NVIDIA 417.71' Move vertex to edit "shape key" , and use "option menu" to change transform value cause blender crash. But it do not happen, when I edit "base shape" . ![proportionalcrash.JPG](https://archive.blender.org/developer/F6701871/proportionalcrash.JPG) **Exact steps for others to reproduce the error** 1 open this blend file (as simple as possible). [shapekey_propotionaledit.blend](https://archive.blender.org/developer/F6701924/shapekey_propotionaledit.blend) 2 move current active vertex (edit) with move (rotate, transform, scale) tool . 3 Open pop up option menu, and try to change x, y, z value of option menu. it cause crash. 4 Same crash happen about "roate , move, scale" tool, when edit property values of each tool option. 5 If I remove shape keys, change values cause no issue.

takeshi funahashi commented

2019-02-24 07:58:29 +01:00

Added subscriber: @TakeshiFunahashi

takeshi funahashi changed title from ~~Proportional editing for shape key ,change tool option menu values cause crash~~ to Edit mesh for shape key ,change tool option menu values cause crash

2019-02-24 08:24:54 +01:00

takeshi funahashi commented

2019-02-24 12:26:52 +01:00

I summarize key points

1 The mesh(eg default cube) have at least one "shape key" (include mesh which only have " base" shape key)

2 "apply shape keys to edit" option "ON"

3 In edit mode, use move (rotate, scale) tools to edit mesh, then change "floating Operator Panel" property values of current tool.

4 it cause crash about recent 2.8 builds.

5 if "apply shape keys to edit option " is "OFF", it work. but I can not edit" shape key" with correct visula infomation.

It happen about recent 2.8 builds
not happen about recent 2.7 builds and F6 menu.

I summarize key points 1 The mesh(eg default cube) have at least one "shape key" (include mesh which only have " base" shape key) 2 "apply shape keys to edit" option "ON" 3 In edit mode, use move (rotate, scale) tools to edit mesh, then change "floating Operator Panel" property values of current tool. 4 it cause crash about recent 2.8 builds. 5 if "apply shape keys to edit option " is "OFF", it work. but I can not edit" shape key" with correct visula infomation. It happen about recent 2.8 builds not happen about recent 2.7 builds and F6 menu.

Jacques Lucke commented

2019-02-25 14:01:42 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-02-25 14:01:42 +01:00

I can't reproduce the issue in my Blender build. Can you check if the bug still exists in todays build?

takeshi funahashi commented

2019-02-26 05:12:32 +01:00

Jacques Thanks to take your time . I up-date and build 2.8 now. but it still show same crash.
Just to confitm, did you set "Apply shape keys in edit mode " as Active?

I just test default cube again , and add only one shape key (default it named as base), then "Apply shape keys in edit mode" as Active. (though if there is only one shape key, it have no mean, but to test easy)
this option is usually used to edit active shape key, with keep other shape key defomation)

In edit mode ,move one vertice, and change value of Context menu, (direct input or use mouse slide), blender shut down. (sometimes freeze once, then shut down)

Jacques Thanks to take your time . I up-date and build 2.8 now. but it still show same crash. Just to confitm, did you set "Apply shape keys in edit mode " as Active? ![crash.JPG](https://archive.blender.org/developer/F6715232/crash.JPG) I just test default cube again , and add only one shape key (default it named as base), then "Apply shape keys in edit mode" as Active. (though if there is only one shape key, it have no mean, but to test easy) this option is usually used to edit active shape key, with keep other shape key defomation) In edit mode ,move one vertice, and change value of Context menu, (direct input or use mouse slide), blender shut down. (sometimes freeze once, then shut down)

takeshi funahashi commented

2019-02-26 05:37:32 +01:00

I test with dbug-all mode. with default cube. (this time add one shape key with base) but crash. and show EXCEPTION_ACCESS_VIOLATION Error This log help to find problem?

wm_event_do_handlers: Handling event
wmEvent type:220 / RET, val:1 / PRESS,

       shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0,
       mouse:(633,199), ascii:' ', utf8:'', keymap_idname:(null), pointer:00000222D83286A8

graph_id_tag_update: id=WMWinMan flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=WMWinMan flags=COPY_ON_WRITE source=USER_EDIT
graph_id_tag_update: id=WMWinMan flags=TRANSFORM, GEOMETRY source=USER_EDIT
graph_id_tag_update: id=WMWinMan flags=TRANSFORM, GEOMETRY source=USER_EDIT
redo_cb: operator redo Move
graph_id_tag_update: id=OBCube flags=GEOMETRY source=USER_EDIT
graph_id_tag_update: id=OBCube flags=GEOMETRY source=USER_EDIT
graph_id_tag_update: id=MECube flags=LEGACY_0 source=USER_EDIT
graph_id_tag_update: id=KEKey flags=LEGACY_0 source=USER_EDIT
graph_id_tag_update: id=OBCube flags=GEOMETRY source=USER_EDIT
graph_id_tag_update: id=OBCube flags=GEOMETRY source=USER_EDIT
graph_id_tag_update: id=MECube flags=LEGACY_0 source=USER_EDIT
graph_id_tag_update: id=KEKey flags=LEGACY_0 source=USER_EDIT
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF782E040C0
Module : C:\myprograms\blender-git\build_windows_Release_x64_vc15_Release\bin\Release\blender.exe

I test with dbug-all mode. with default cube. (this time add one shape key with base) but crash. and show EXCEPTION_ACCESS_VIOLATION Error This log help to find problem? wm_event_do_handlers: Handling event wmEvent type:220 / RET, val:1 / PRESS, ``` shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0, mouse:(633,199), ascii:' ', utf8:'', keymap_idname:(null), pointer:00000222D83286A8 ``` graph_id_tag_update: id=WMWinMan flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=WMWinMan flags=COPY_ON_WRITE source=USER_EDIT graph_id_tag_update: id=WMWinMan flags=TRANSFORM, GEOMETRY source=USER_EDIT graph_id_tag_update: id=WMWinMan flags=TRANSFORM, GEOMETRY source=USER_EDIT redo_cb: operator redo Move graph_id_tag_update: id=OBCube flags=GEOMETRY source=USER_EDIT graph_id_tag_update: id=OBCube flags=GEOMETRY source=USER_EDIT graph_id_tag_update: id=MECube flags=LEGACY_0 source=USER_EDIT graph_id_tag_update: id=KEKey flags=LEGACY_0 source=USER_EDIT graph_id_tag_update: id=OBCube flags=GEOMETRY source=USER_EDIT graph_id_tag_update: id=OBCube flags=GEOMETRY source=USER_EDIT graph_id_tag_update: id=MECube flags=LEGACY_0 source=USER_EDIT graph_id_tag_update: id=KEKey flags=LEGACY_0 source=USER_EDIT Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF782E040C0 Module : C:\myprograms\blender-git\build_windows_Release_x64_vc15_Release\bin\Release\blender.exe

takeshi funahashi commented

2019-02-26 10:48:37 +01:00

blenderest.wmv

I attach video (wmv). Though in movie, I input values (and wrong values first,,) but it not matter.
slider can not work too.

[blenderest.wmv](https://archive.blender.org/developer/F6716244/blenderest.wmv) I attach video (wmv). Though in movie, I input values (and wrong values first,,) but it not matter. slider can not work too.

Jacques Lucke commented

2019-02-26 11:30:27 +01:00

I still can't reproduce it, not sure what I'm doing wrong.

Yes, this option is checked.

I see that you compiled Blender yourself, can you try if the same problem happens in the buildbot build?

I still can't reproduce it, not sure what I'm doing wrong. Yes, this option is checked. I see that you compiled Blender yourself, can you try if the same problem happens in the buildbot build?

takeshi funahashi commented

2019-02-26 12:34:01 +01:00

Hmm,,

I do not think, it is caused my compile process. because I see no problem when build with Cmake.
Anyway I tried as you suggested, download recent 2.8 build zip, from buildbot for windows 64bit ,then run it.
But just see same crash.

I have tried to un-activate all add on, and return as factory setting then test thing with default cube.
but it still not work for me.

As you can see, it is really easy process. Then at current I have no way to offer more report which you can find.
at first I thought it caused with proportional edit, or armatrure appleid etc.
But it happen as I discribed, about default cube, and shape key. Then is there way to attach log of this crush with more detail, if it is caused my pc side? I up-date driver too(Nvidia).

Hmm,, I do not think, it is caused my compile process. because I see no problem when build with Cmake. Anyway I tried as you suggested, download recent 2.8 build zip, from buildbot for windows 64bit ,then run it. But just see same crash. I have tried to un-activate all add on, and return as factory setting then test thing with default cube. but it still not work for me. As you can see, it is really easy process. Then at current I have no way to offer more report which you can find. at first I thought it caused with proportional edit, or armatrure appleid etc. But it happen as I discribed, about default cube, and shape key. Then is there way to attach log of this crush with more detail, if it is caused my pc side? I up-date driver too(Nvidia).

takeshi funahashi commented

2019-02-26 14:10:09 +01:00

Thank to take time,,
Then about my first attached blend file, I forgot to keep activate "Apply shape keys in edit mode" for my test.
So if you test with first one, untill you set it as active, this problem are hidden. Then I re-make blend file to test easy. so other one need to test,, use it please.

To test, open the blend file in 2.8, and translate currently selected area. with gizmo. (now proportion edit is active too)

then change the (F6 of 2.7) history property X Y Z values.As my test, crash happen when I change proportional edit mode , and Orientation mode, too. Anyway I wait other report.
shapekey_propotionaledit.blend

Thank to take time,, Then about my first attached blend file, I forgot to keep activate "Apply shape keys in edit mode" for my test. So if you test with first one, untill you set it as active, this problem are hidden. Then I re-make blend file to test easy. so other one need to test,, use it please. To test, open the blend file in 2.8, and translate currently selected area. with gizmo. (now proportion edit is active too) then change the (F6 of 2.7) history property X Y Z values.As my test, crash happen when I change proportional edit mode , and Orientation mode, too. Anyway I wait other report. [shapekey_propotionaledit.blend](https://archive.blender.org/developer/F6717272/shapekey_propotionaledit.blend)

Sebastian Parborg commented

2019-02-26 14:57:58 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-02-26 14:57:58 +01:00

I can't seem to reproduce this either. Even with the latest .blend test file, it doesn't crash for me if I change the X Y Z values or the other options in the pop up.

I don't really know what could be wrong so I'm just trying to see if we can figure this out.

Does it happen if you don't type in the values? So you either click and drag with the mouse on the X Y Z value or use the arrows on the side of the input box?

I can't seem to reproduce this either. Even with the latest .blend test file, it doesn't crash for me if I change the X Y Z values or the other options in the pop up. I don't really know what could be wrong so I'm just trying to see if we can figure this out. Does it happen if you don't type in the values? So you either click and drag with the mouse on the X Y Z value or use the arrows on the side of the input box?

takeshi funahashi commented

2019-02-26 16:50:52 +01:00

So I really lost a way. but thanks you test too.

I see same crash with drag mouse, or use arrows to change value. so it is not matter.
when I change values in the pop up menu with 2.8, about shape key in edit mode, it must happen.

At first time I see this effect, when I make add on to set auto-cursor for armature modified skin.
And I hoped to change proportional edit radius from UI. and remember, the window offer the option.
then just change the radius, it cause crash.

I felt I need to report it and test with each case. after that I found it happen with defautl cube, and shape keys.
I re-open the file now, and do samething, it immediately crash. but about other things I have not seen any difference as same as other user and report. I tried to remove my pen tab too. (I often use pen with mouse at same time)

If I need to add my setting file or there is something I can try , I may attach them. so please tell me anything which you need to know.

So I really lost a way. but thanks you test too. I see same crash with drag mouse, or use arrows to change value. so it is not matter. when I change values in the pop up menu with 2.8, about shape key in edit mode, it must happen. At first time I see this effect, when I make add on to set auto-cursor for armature modified skin. And I hoped to change proportional edit radius from UI. and remember, the window offer the option. then just change the radius, it cause crash. I felt I need to report it and test with each case. after that I found it happen with defautl cube, and shape keys. I re-open the file now, and do samething, it immediately crash. but about other things I have not seen any difference as same as other user and report. I tried to remove my pen tab too. (I often use pen with mouse at same time) If I need to add my setting file or there is something I can try , I may attach them. so please tell me anything which you need to know.

takeshi funahashi commented

2019-02-26 17:00:25 +01:00

It is current test with up-load scene. I just re-load scene. and video decode. Do you have some idea, what I may need to try?

blenderest.wmv

It is current test with up-load scene. I just re-load scene. and video decode. Do you have some idea, what I may need to try? [blenderest.wmv](https://archive.blender.org/developer/F6717914/blenderest.wmv)

Sebastian Parborg commented

2019-02-26 17:30:02 +01:00

I guess we can try and see if it help to temporarily remove your current config files.

Go to %USERPROFILE%\AppData\Roaming\Blender Foundation\Blender and rename the folder 2.80 to 2.80 backup.

This should make blender create a new 2.80 folder with the default configs. Does the problem still happen after you have done this?

When you are done, you can just remove the new 2.80 folder and rename the 2.80 backup to 2.80 again.

I guess we can try and see if it help to temporarily remove your current config files. Go to `%USERPROFILE%\AppData\Roaming\Blender Foundation\Blender` and rename the folder `2.80` to `2.80 backup`. This should make blender create a new `2.80` folder with the default configs. Does the problem still happen after you have done this? When you are done, you can just remove the new `2.80` folder and rename the `2.80 backup` to `2.80` again.

Andrew Charlton commented

2019-02-26 23:59:06 +01:00

Added subscriber: @Scaredyfish

Andrew Charlton commented

2019-02-26 23:59:06 +01:00

I can reproduce this in most recent build. Removing config makes no difference. system-info-02-27.txt

I can reproduce this in most recent build. Removing config makes no difference. [system-info-02-27.txt](https://archive.blender.org/developer/F6719563/system-info-02-27.txt)

takeshi funahashi commented

2019-02-27 04:25:37 +01:00

I rename 2.8 folda in appData and, it load default blender setting start scene. (no add on, and all setting change as blender default,, (left-click to r-click, and font size etc)

then I test with new cube. but when I change value, immediately blender 2.8 crash.
I test with most of --debug mode, but after all I only see, access vioration erroer.

And thanks Andrew Charlton confirm ,, I try to pause anti virus soft too,,,
system-info_report.txt

I rename 2.8 folda in appData and, it load default blender setting start scene. (no add on, and all setting change as blender default,, (left-click to r-click, and font size etc) then I test with new cube. but when I change value, immediately blender 2.8 crash. I test with most of --debug mode, but after all I only see, access vioration erroer. And thanks Andrew Charlton confirm ,, I try to pause anti virus soft too,,, [system-info_report.txt](https://archive.blender.org/developer/F6720901/system-info_report.txt)

Sebastian Parborg commented

2019-02-27 09:16:52 +01:00

Added subscriber: @LazyDodo

Sebastian Parborg commented

2019-02-27 09:16:52 +01:00

@LazyDodo can you reproduce this?

Ray molenkamp commented

2019-02-27 14:56:01 +01:00

I can't repro either but given he does his own builds.... make a build with make full debug and try reproducing it with that version, when it crashes it should print out stacktrace where the error originated.

I can't repro either but given he does his own builds.... make a build with `make full debug` and try reproducing it with that version, when it crashes it should print out stacktrace where the error originated.

takeshi funahashi commented

2019-02-27 18:31:28 +01:00

@LazyDodo
Usually I use "make release" for CUDA kernels but anyway I tried to make a build with "make full debug" version as you suggested.

Then when I run the version blender.exe I get this erroer.

@LazyDodo Usually I use "make release" for CUDA kernels but anyway I tried to make a build with "make full debug" version as you suggested. Then when I run the version blender.exe I get this erroer. ![runerror.JPG](https://archive.blender.org/developer/F6724660/runerror.JPG)

takeshi funahashi commented

2019-02-27 18:49:04 +01:00

And I up-date java , then hide 2.80 script folda again. and run again. now I can run this version (full debug mode build).

After that do same test. now I got this erroer. and blender freeze.

C:\myprograms\blender-git\build_windows_Full_x64_vc15_Debug\bin\Debug>blender.exe --debug
Switching to fully guarded memory allocator.
Blender 2.80 (sub 45)
Build: 2019/02/28 02:21 Windows
argv- [x] = blender.exe
argv- [x] = --debug
read file

Version 280 sub 39 date unknown hash unknown

Vendor: NVIDIA Corporation
Renderer: GeForce GTX 980 Ti/PCIe/SSE2
Version: 4.5.0 NVIDIA 419.17
Warning! Dummy Version: 4.6.0 NVIDIA 419.17
Context Version: 4.5
Vendor: NVIDIA Corporation
Renderer: GeForce GTX 980 Ti/PCIe/SSE2
Version: 4.5.0 NVIDIA 419.17
Warning! Dummy Version: 4.6.0 NVIDIA 419.17
Context Version: 4.5
found bundled python: C:\myprograms\blender-git\build_windows_Full_x64_vc15_Debug\bin\Debug\2.80\python
redo_cb: operator redo Move
29: BLI_system_backtrace - 0x45FE3310
28: CustomData_get_active_layer_index - 0x45924820
27: CustomData_get_offset - 0x45924480
26: BM_mesh_bm_to_me_for_eval - 0x452D9290
25: BKE_mesh_from_bmesh_for_eval_nomain - 0x45943DE0
24: BKE_mesh_from_editmesh_with_coords_thin_wrap - 0x45943E40
23: BKE_crazyspace_get_first_deform_matrices_editbmesh - 0x45994990
22: createTransEditVerts - 0x44876120
21: createTransData - 0x44868ED0
20: initTransform - 0x448204D0
19: transformops_data - 0x44808C10
18: transform_exec - 0x44809010
17: wm_operator_exec - 0x4459D2F0
16: WM_operator_repeat - 0x44596B40
15: ED_undo_operator_repeat - 0x445E52C0
14: ED_undo_operator_repeat_cb_evt - 0x445E5720
13: ui_apply_but_funcs_after - 0x449760F0
12: ui_handler_region_menu - 0x44974D60
11: wm_handler_ui_call - 0x4459C850
10: wm_handlers_do_intern - 0x445A03A0
9: wm_handlers_do - 0x445A14A0
8: wm_event_do_handlers - 0x44599730
7: WM_main - 0x44576530
6: main - 0x4456E440
5: invoke_main - 0x4A6A1F40
4: __scrt_common_main_seh - 0x4A6A1CF0
3: __scrt_common_main - 0x4A6A1CD0
2: mainCRTStartup - 0x4A6A2000
1: BaseThreadInitThunk - 0x5383DB0
0: RtlUserThreadStart - 0x6A43670
BLI_assert failed: c:\myprograms\blender-git\blender\source\blender\blenkernel\intern\customdata.c:1709, CustomData_get_active_layer_index(), at 'customdata_typemap_is_valid(data)'

And this is generated blender.crush.txt
blender.crash.txt

And I up-date java , then hide 2.80 script folda again. and run again. now I can run this version (full debug mode build). After that do same test. now I got this erroer. and blender freeze. C:\myprograms\blender-git\build_windows_Full_x64_vc15_Debug\bin\Debug>blender.exe --debug Switching to fully guarded memory allocator. Blender 2.80 (sub 45) Build: 2019/02/28 02:21 Windows argv- [x] = blender.exe argv- [x] = --debug read file ``` Version 280 sub 39 date unknown hash unknown ``` Vendor: NVIDIA Corporation Renderer: GeForce GTX 980 Ti/PCIe/SSE2 Version: 4.5.0 NVIDIA 419.17 Warning! Dummy Version: 4.6.0 NVIDIA 419.17 Context Version: 4.5 Vendor: NVIDIA Corporation Renderer: GeForce GTX 980 Ti/PCIe/SSE2 Version: 4.5.0 NVIDIA 419.17 Warning! Dummy Version: 4.6.0 NVIDIA 419.17 Context Version: 4.5 found bundled python: C:\myprograms\blender-git\build_windows_Full_x64_vc15_Debug\bin\Debug\2.80\python redo_cb: operator redo Move 29: BLI_system_backtrace - 0x45FE3310 28: CustomData_get_active_layer_index - 0x45924820 27: CustomData_get_offset - 0x45924480 26: BM_mesh_bm_to_me_for_eval - 0x452D9290 25: BKE_mesh_from_bmesh_for_eval_nomain - 0x45943DE0 24: BKE_mesh_from_editmesh_with_coords_thin_wrap - 0x45943E40 23: BKE_crazyspace_get_first_deform_matrices_editbmesh - 0x45994990 22: createTransEditVerts - 0x44876120 21: createTransData - 0x44868ED0 20: initTransform - 0x448204D0 19: transformops_data - 0x44808C10 18: transform_exec - 0x44809010 17: wm_operator_exec - 0x4459D2F0 16: WM_operator_repeat - 0x44596B40 15: ED_undo_operator_repeat - 0x445E52C0 14: ED_undo_operator_repeat_cb_evt - 0x445E5720 13: ui_apply_but_funcs_after - 0x449760F0 12: ui_handler_region_menu - 0x44974D60 11: wm_handler_ui_call - 0x4459C850 10: wm_handlers_do_intern - 0x445A03A0 9: wm_handlers_do - 0x445A14A0 8: wm_event_do_handlers - 0x44599730 7: WM_main - 0x44576530 6: main - 0x4456E440 5: invoke_main - 0x4A6A1F40 4: __scrt_common_main_seh - 0x4A6A1CF0 3: __scrt_common_main - 0x4A6A1CD0 2: mainCRTStartup - 0x4A6A2000 1: BaseThreadInitThunk - 0x5383DB0 0: RtlUserThreadStart - 0x6A43670 BLI_assert failed: c:\myprograms\blender-git\blender\source\blender\blenkernel\intern\customdata.c:1709, CustomData_get_active_layer_index(), at 'customdata_typemap_is_valid(data)' And this is generated blender.crush.txt [blender.crash.txt](https://archive.blender.org/developer/F6724781/blender.crash.txt)

takeshi funahashi commented

2019-02-27 19:28:34 +01:00

Then for more precise report, would not you offer "Proper procedure to generate "stack trace" after build this" full debug" version?

Though it is usuall for developer, as User I do not know eg I should run blender.exe from console with --debug mode, or just run as I like. then where file will be generated when crush occur ,and developer need which one?

eg you may need to see blender.crash.txt, or log in command prompt?

Then for more precise report, would not you offer "Proper procedure to generate "stack trace" after build this" full debug" version? Though it is usuall for developer, as User I do not know eg I should run blender.exe from console with --debug mode, or just run as I like. then where file will be generated when crush occur ,and developer need which one? eg you may need to see blender.crash.txt, or log in command prompt?

Sebastian Parborg commented

2019-02-28 16:58:14 +01:00

It seems like it crashes because the mesh lacks some vital data. However this doesn't seem to happen for any of the devs that tried to reproduce this, so I don't know were to go from there really...

takeshi funahashi commented

2019-03-01 03:14:59 +01:00

When I change property of the history propert menu with option "Apply shape keys in edit mode" ,
blender clash ,or freeze after all clash, and get this message.So it is not only about transform values.

Then everytime I get this log, (all 2.8 recent versions, with use full-debug build and default setting (no add on)

BLI_assert failed: c:\myprograms\blender-git\blender\source\blender\blenkernel\intern\customdata.c:1709, CustomData_get_active_layer_index(), at 'customdata_typemap_is_valid(data)'

When I change property of the history propert menu with option "Apply shape keys in edit mode" , blender clash ,or freeze after all clash, and get this message.So it is not only about transform values. Then everytime I get this log, (all 2.8 recent versions, with use full-debug build and default setting (no add on) BLI_assert failed: c:\myprograms\blender-git\blender\source\blender\blenkernel\intern\customdata.c:1709, CustomData_get_active_layer_index(), at 'customdata_typemap_is_valid(data)'

Campbell Barton commented

2019-03-06 02:12:47 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2019-03-06 02:12:47 +01:00

Can redo here, strange others couldn't redo - it crashes immediately here w/ address sanitizer enabled.

The crash is caused by using an outdated evaluated mesh, submitted fix D4455.

Can redo here, strange others couldn't redo - it crashes immediately here w/ address sanitizer enabled. The crash is caused by using an outdated evaluated mesh, submitted fix [D4455](https://archive.blender.org/developer/D4455).

takeshi funahashi commented

2019-03-06 02:26:59 +01:00

Thanks Canmpbell you find this report and finally confrimed by developer

I suspect my first report did not discribe , this clush happen with "apply shape keys to edit" option "ON".
Then I added detail steps and case later, but did not edit top subject . And yes to be frankly said, I felt strange, why most of others could not redo. If there are condtions, by which I can avoid this clash, I hope to know way, untill fix.

Thanks Canmpbell you find this report and finally confrimed by developer I suspect my first report did not discribe , this clush happen with "apply shape keys to edit" option "ON". Then I added detail steps and case later, but did not edit top subject . And yes to be frankly said, I felt strange, why most of others could not redo. If there are condtions, by which I can avoid this clash, I hope to know way, untill fix.

blender-admin commented

2019-05-28 16:05:32 +02:00

This issue was referenced by e256bc2250

This issue was referenced by e256bc22503772b4550fadb778e8247dc26f905f

Sergey Sharybin commented

2019-05-28 17:11:23 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2019-05-28 17:11:23 +02: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

Edit mesh for shape key ,change tool option menu values cause crash #61904