[Bug]: Segfault on reload/document change

[bodby]

Is there an existing issue for this?

• I have searched the existing issues

Problem

I don't know whether to mark this as a duplicate of #462, since this crash happens on the first reload and not multiple consecutive ones (please close if it is a duplicate).

When using latexmk -pdf -pvc and opening the resultant file in Zathura, any changes to the file or even pressing Shift+R causes a segfault.

I have tried using filemonitor noop and signal instead of glib, but all of them segfault when the file changes.

Steps to reproduce

1. Open PDF for generated LaTeX file in Zathura.
2. Recompile PDF file (even with no changes).
3. Crash. :(

Expected behavior

No segfault when reloading/file changes.

zathura version (zathura --version)

0.5.11

girara version (zathura --version)

0.4.5

zathura backend

poppler

[bodby]

GDB backtrace output (never used GDB before so please tell if more info. is needed):

warning: Can't open file /memfd:sljit (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:gdk-wayland (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:wayland-cursor (deleted) during file-backed mapping note processing

...

[New LWP 5873]
[New LWP 5880]
[New LWP 5879]
[New LWP 5877]
[New LWP 5876]
[New LWP 5875]
[New LWP 5874]
[New LWP 5878]
Core was generated by `/nix/store/mdvy27myhj3q669k9fjl2b02f6axhcs5-zathura-0.5.11-bin/bin/.zathura-wrapped hehe.pdf'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000000000041987b in ?? ()
[Current thread is 1 (LWP 5873)]
(gdb) bt full
#0  0x000000000041987b in ?? ()
No symbol table info available.
#1  0x0000000008198205 in ?? ()
No symbol table info available.
#2  0x000000000041fffd in ?? ()
No symbol table info available.
#3  0x0000000000000000 in ?? ()
No symbol table info available.

[bodby]

Just tried changing a file again and got this message before the segfault:

These are both called by zathura/callbacks.c on lines 63 and 64.

I also got different error messages before (that I forgot to save...) so I feel like this is something related to async messing up somewhere.