Gjs-CRITICAL **: Attempting to run a JS callback during shutdown

Description

Each time foliate closes, these errors are emitted in the system journal.

No other issue noted while running/using the app.

May 12 14:58:48 foliate[1663296]: Attempting to run a JS callback during shutdown. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
                                  The offending callback was ListBoxUpdateHeaderFunc().
                                  == Stack trace for context 0x63ae182e11f0 ==
May 12 14:58:48 foliate[1663296]: Attempting to run a JS callback during shutdown. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
                                  The offending callback was ListBoxUpdateHeaderFunc().
                                  == Stack trace for context 0x63ae182e11f0 ==
May 12 14:58:48 foliate[1663296]: Attempting to run a JS callback during shutdown. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
                                  The offending callback was ListBoxUpdateHeaderFunc().
                                  == Stack trace for context 0x63ae182e11f0 ==
May 12 14:58:48 foliate[1663296]: Attempting to run a JS callback during shutdown. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
                                  The offending callback was ListBoxUpdateHeaderFunc().
                                  == Stack trace for context 0x63ae182e11f0 ==
May 12 14:58:48 foliate[1663296]: Attempting to run a JS callback during shutdown. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
                                  The offending callback was ListBoxUpdateHeaderFunc().
                                  == Stack trace for context 0x63ae182e11f0 ==
May 12 14:58:48 foliate[1663296]: Attempting to run a JS callback during shutdown. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
                                  The offending callback was ListBoxUpdateHeaderFunc().
                                  == Stack trace for context 0x63ae182e11f0 ==
May 12 14:58:48 foliate[1663296]: Attempting to run a JS callback during shutdown. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
                                  The offending callback was ListBoxUpdateHeaderFunc().
                                  == Stack trace for context 0x63ae182e11f0 ==

Steps To Reproduce

1. Exit the app

Expected behavior

Exit cleanly.

Version:

• kernel 6.14.6
• gnome-shell 48.1 (Wayland)
• mutter 48.2 (-Dxwayland=false -Dx11=false)
• gtk4 4.18.4 (-Dx11-backend=false)
• foliate 3.3.0