+- Wings 3D Development Forum (https://www.wings3d.com/forum)
+-- Forum: Wings 3D (https://www.wings3d.com/forum/forumdisplay.php?fid=1)
+--- Forum: Bug Reports (https://www.wings3d.com/forum/forumdisplay.php?fid=12)
+--- Thread: [fixed] Wings_crash.dump - function_clause (/showthread.php?tid=2536)
RE: [standby] Wings_crash.dump - function_clause - Hank - 08-07-2018
(08-06-2018, 08:28 PM)micheus Wrote: What I can confirm is that the issue is related to the Geometry window lost the focus and never get it back.
you can get the keys working again if (for example) pallette window is moved to geometry graph area - then something is refreshing the status and you can use repeat last function (key: d) again. Geometry graph top bar is still 'unselected' and the problem is coming back after few operations, so it's only temporary solution. Maybe this step can give more debug data?
BR, Hank
RE: [standby] Wings_crash.dump - function_clause - micheus - 08-07-2018
Hank said he doesn't uses Auto-Save enabled, so by using his preferences file I was also able to get the stack trace after a couple of tries:
Code:
Grabbed focus lost: {wx_ref,555,wxGLCanvas,[]} geom
Stack trace: [{wings_util,'-array_greatest_key/1-fun-0-',3,
[{file,"f:/unixlike/src/wings/src/wings_util.erl"},
{line,170}]},
{array,sparse_foldr_3,6,[{file,"array.erl"},{line,1848}]},
{array,sparse_foldr_2,8,[{file,"array.erl"},{line,1837}]},
{wings_util,array_greatest_key,1,
[{file,"f:/unixlike/src/wings/src/wings_util.erl"},
{line,170}]},
{wings_we,update_id_bounds,1,
[{file,"f:/unixlike/src/wings/src/wings_we.erl"},
{line,806}]},
{wings_ff_wings,share_list_2,3,
[{file,"f:/unixlike/src/wings/src/wings_ff_wings.erl"},
{line,1008}]},
{wings_ff_wings,import_objects,5,
[{file,"f:/unixlike/src/wings/src/wings_ff_wings.erl"},
{line,753}]},
{wings_ff_wings,import_objects,3,
[{file,"f:/unixlike/src/wings/src/wings_ff_wings.erl"},
{line,721}]},
{wings_ff_wings,import,2,
[{file,"f:/unixlike/src/wings/src/wings_ff_wings.erl"},
{line,28}]},
{wings_file,'-confirmed_open/2-fun-0-',3,
[{file,"f:/unixlike/src/wings/src/wings_file.erl"},
{line,351}]},
{wings_develop,time_command,2,
[{file,"f:/unixlike/src/wings/src/wings_develop.erl"},
{line,79}]},
{wings,raw_command,4,
[{file,"f:/unixlike/src/wings/src/wings.erl"},
{line,625}]},
{wings_wm,handle_event,3,
[{file,"f:/unixlike/src/wings/src/wings_wm.erl"},
{line,974}]},
{wings_wm,send_event,2,
[{file,"f:/unixlike/src/wings/src/wings_wm.erl"},
{line,940}]},
{wings_wm,do_dispatch,2,
[{file,"f:/unixlike/src/wings/src/wings_wm.erl"},
{line,841}]},
{wings_wm,dispatch_event,1,
[{file,"f:/unixlike/src/wings/src/wings_wm.erl"},
{line,748}]},
{wings_wm,get_and_dispatch,0,
[{file,"f:/unixlike/src/wings/src/wings_wm.erl"},
{line,651}]},
{wings,init_part2,2,
[{file,"f:/unixlike/src/wings/src/wings.erl"},
{line,104}]},
{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]RE: [standby] Wings_crash.dump - function_clause - micheus - 08-07-2018
Isolated/worked around the common part of the log (at top) and the log is now pointing to another place in the code. So, this stack track doesn't help much to find what is firing the process which end up for kill the geometry window focus.
The problem is really in the new code used to fix the old focus issue.
Some unregistered window is taking the focus. With the autosave enabled (which is the easy way to reproduce the issue) that window has the top_frame as parent, but it's not a registered window (not in wm_windows).