Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1470791[details]
abrt log
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):
gjs-1.52.3-1.el7
gnome-documents-3.28.1-1.el7
How reproducible:
100%
Steps to Reproduce:
1. Start gnome-documents
2. Close gnome-documents
3.
Actual results:
Expected results:
Additional info:
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.
gnome-documents-3.28.1-2.el7.x86_64
gnome-documents-libs-3.28.1-2.el7.x86_64
Built gnome-documents-3.28.1-2.el7:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17858873
(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
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.
https://access.redhat.com/errata/RHSA-2018:3140
Created attachment 1470791 [details] abrt log 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): gjs-1.52.3-1.el7 gnome-documents-3.28.1-1.el7 How reproducible: 100% Steps to Reproduce: 1. Start gnome-documents 2. Close gnome-documents 3. Actual results: Expected results: Additional info: