Created attachment 1470791 [details]
Description of problem:
There is a crash when exiting gnome-documents
$ $ gnome-documents
(org.gnome.Documents:13360): Gjs-CRITICAL **: 14:36:17.137: Attempting to run a JS callback during garbage collection. 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.
(org.gnome.Documents:13360): Gjs-CRITICAL **: 14:36:17.137: The offending callback was destroy(), a vfunc.
== Stack trace for context 0x25680b0 ==
zsh: segmentation fault (core dumped) gnome-documents
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start gnome-documents
2. Close gnome-documents
Here's a scratch build:
Exiting the application still takes several second which is kinda unusual time but the most important thing is that the segfault is gone, thanks a lot rishi.
(In reply to Martin Krajnak from comment #5)
> Exiting the application still takes several second which is kinda unusual
Yes, there's 12s timeout.
It's there to prevent gnome-documents' gnome-shell search provider from spawning repeatedly when typing in the overview. With the timeout in place, as long as there's activity within that time period, the same process will be used. It shouldn't affect the normal functioning of the application because it's activated over D-Bus (DBusActivatable=true in the desktop file), and the user should see a new window appear even though the underlying process is the same. There can be bugs, though. :P
No crash in gnome-documents-3.28.1-2
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.