filter.ConditionSatisifed crashes client
Case number: | 954892-2005497 |
Topic: | Developer Preview |
Opened by: | LociOiling |
Status: | Closed |
Type: | Bug |
Opened on: | Friday, July 13, 2018 - 20:27 |
Last modified: | Monday, July 30, 2018 - 19:38 |
The Lua code:
filt = filter.GetNames () print ( #filt .. " conditions or filters" ) for ii = 1, #filt do print ( "#" .. ii .. ", name = \"" .. filt [ ii ] .. "\", satisfied = " .. tostring ( filter.ConditionSatisfied ( filt [ ii ] ) ) ) end
produces the following in log.txt
UNHANDLED EXCEPTION 1: interactive::util::FilterResultCacheable::get_result_condition_passes +57 bytes (no line) 2: standalone::application::luaV2_filter_ConditionSatisfied +368 bytes (no line) 3: luaD_precall +425 bytes (no line) 4: luaV_execute +3242 bytes (no line) 5: luaD_call +99 bytes (no line) 6: lua_call +83 bytes (no line) 7: luaD_rawrunprotected +76 bytes (no line) 8: luaD_pcall +53 bytes (no line) 9: lua_pcall +93 bytes (no line) 10: interactive::application::shared::lua::LuaScripter::exec_string +93 bytes (no line) 11: interactive::application::shared::lua::LuaExec::on_exec +88 bytes (no line) 12: boost::detail::function::void_function_obj_invoker0,std::allocator > const &>,boost::_bi::list2,boost::_bi::value,std::allocator > > > >,void>::invoke +22 bytes (no line) 13: boost::function0::operator() +120 bytes (no line) 14: interactive::util::Thread::thread_entry_func +69 bytes (no line) 15: interactive::util::Thread::win32_thread_startup_helper +11 bytes (no line) 16: BaseThreadInitThunk +36 bytes (no line) 17: RtlValidSecurityDescriptor +282 bytes (no line) 18: RtlValidSecurityDescriptor +234 bytes (no line) Sending SOPs:
It's not clear if the Lua example is correct, but it shouldn't cause a crash, regardless.
»
Mon, 07/30/2018 - 19:38
#2
Status: Open » Closed |
Closing, the issue is resolved in 20180725-d14dae34c3-win_x86-devprev, and I'm optimistic that this release will stick.
Lost the mention of 20180711-7bdda27475-win_x86-devprev in the previous, also full log.txt attached to this one. Using puzzle 1546 as a test case. No debug.txt was generated.