After code_convert_string_norecord the callstack is the same as the callstack of the JSON parsing (it uses the same method to convert/validate the string).  



On Sun, 24 Mar 2019, 13:20 Eli Zaretskii, <eliz@gnu.org> wrote:
On March 24, 2019 11:35:25 AM GMT+02:00, yyoncho <yyoncho@gmail.com> wrote:
> Hi Eli,
>
> The callstack is pretty much the same, here are the relevant parts:
>
>    [-] code_convert_string_norecord@0x000055555565e30d (coding.c:9488)
>     [-] module_make_string@0x00005555557d8f0d (emacs-module.c:597)
>     [-] emacs::convert::<impl emacs::IntoLisp<’e> for &’a
> T>::into_lisp@0x00007fffdeafe8c1 (Unknown source)
>   [-] emacs_json_lsp::json_to_lisp@0x00007fffdeb0117e (Unknown source)
>   [-] emacs_json_lsp::json_to_lisp@0x00007fffdeb0169f (Unknown source)
>   [-] emacs_json_lsp::json_to_lisp@0x00007fffdeb012b3 (Unknown source)
>   [-] emacs_json_lsp::json_to_lisp@0x00007fffdeb0169f (Unknown source)
>   [-] emacs_json_lsp::json_to_lisp@0x00007fffdeb0169f (Unknown source)
>   [-] emacs_json_lsp::parse_string@0x00007fffdeb019a9 (Unknown source)
>   [-] std::panicking::try::do_call@0x00007fffdeb02a9f (Unknown source)
>  [-] __rust_maybe_catch_panic@0x00007fffdeb2f26a (src/libpanic_unwind/
> lib.rs:102)
>     [-] <emacs::CallEnv as
> emacs::func::HandleCall>::handle_call@0x00007fffdeb0277a (Unknown
> source)
>    [-] emacs_json_lsp::init::extern_lambda@0x00007fffdeb01cc4 (Unknown
> source)
>
> Thanks,
> Ivan
>
> On Sun, Mar 24, 2019 at 5:32 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > > From: yyoncho <yyoncho@gmail.com>
> > > Date: Sat, 23 Mar 2019 23:04:18 +0200
> > > Cc: Sébastien Chapuis <sebastien@chapu.is>,
> > >       31138@debbugs.gnu.org
> > >
> > > I will try with run-hooks = nil. (I still cannot reproduce the
> issue
> > consistently). As a side note, I think that similar
> > > issue affects emacs dynamic modules based on my limited testing.
> Please
> > reply back if you need a callstack.
> >
> > Yes, a callstack in the case of modules would be helpful (although I
> > think I can guess where it will point).
> >
> > Thanks.
> >

Thanks, but where is the call to the hook which iscthe source of the problem?  I don't even see Fkill_buffer in the backtrace.  What am I missing?