munmap_chunk(): invalid pointer

[Ambrevar]

Nyxt crashes when loading web pages, see
atlas-engineer/nyxt#1251 (comment):

<INFO> [13:55:44] Loading "https://startpage.com/".
munmap_chunk(): invalid pointer
Unhandled SB-INT:SIMPLE-PROGRAM-ERROR in thread #<SB-THREAD:THREAD "cl-cffi-gtk main thread" RUNNING
                                                   {100780E733}>:
  invalid number of arguments: 1

Backtrace for: #<SB-THREAD:THREAD "cl-cffi-gtk main thread" RUNNING {100780E733}>
0: ((LAMBDA (NYXT::WEB-VIEW USER-DATA) :IN FFI-BUFFER-MAKE) #<CL-WEBKIT2:WEBKIT-WEB-VIEW {100F882A53}>) [external]
1: (GOBJECT::CALL-WITH-RESTARTS #<FUNCTION (LAMBDA (NYXT::WEB-VIEW USER-DATA) :IN FFI-BUFFER-MAKE) {5222560B}> (#<CL-WEBKIT2:WEBKIT-WEB-VIEW {100F882A53}>))
2: ((LAMBDA (GOBJECT::CLOSURE GOBJECT::RETURN-VALUE GOBJECT::COUNT-OF-ARGS GOBJECT::ARGS GOBJECT::INVOCATION-HINT GOBJECT::MARSHAL-DATA) :IN "/gnu/store/rackncfj42yzd9v3gk2pyhlnaqgfwgq3-sbcl-cl-cffi-gtk-0.11.2-3.c4d5396/share/common-lisp/sbcl/cl-cffi-gtk/gobject/gobject.signals.lisp") #.(SB-SYS:INT-SAP #X7F33602F3990) #.(SB-SYS:INT-SAP #X7F336F316200) 1 #.(SB-SYS:INT-SAP #X7F336F3162B0) #<unused argument> #<unused argument>)
3: ((LAMBDA (SB-ALIEN::ARGS-POINTER SB-ALIEN::RESULT-POINTER FUNCTION) :IN "/gnu/store/rackncfj42yzd9v3gk2pyhlnaqgfwgq3-sbcl-cl-cffi-gtk-0.11.2-3.c4d5396/share/common-lisp/sbcl/cl-cffi-gtk/gobject/gobject.signals.lisp") #<unavailable argument> #<unavailable argument> #<unavailable argument>)
4: ("foreign function: funcall_alien_callback")
5: ("foreign function: callback_wrapper_trampoline")
6: ("foreign function: #x5010086B")
7: ((LAMBDA NIL :IN GTK:ENSURE-GTK-MAIN))
8: ((LAMBDA NIL :IN BORDEAUX-THREADS::BINDING-DEFAULT-SPECIALS))
9: ((FLET SB-UNIX::BODY :IN SB-THREAD::RUN))
10: ((FLET "WITHOUT-INTERRUPTS-BODY-11" :IN SB-THREAD::RUN))
11: ((FLET SB-UNIX::BODY :IN SB-THREAD::RUN))
12: ((FLET "WITHOUT-INTERRUPTS-BODY-4" :IN SB-THREAD::RUN))
13: (SB-THREAD::RUN)
14: ("foreign function: call_into_lisp")
15: ("foreign function: funcall1")

This does not happen on e9a46df.

The crash occurs with c4d5396, so I guess the issue was introduced in just one of the last few commits.

Any idea?