Bug 2239238

Summary: [abrt] gjs: slab_allocator_free_chunk(): gjs-console killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Tadej Janež <tadej.j>
Component: gjsAssignee: Colin Walters <walters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: fzatlouk, gnome-sig, otaylor, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a61bac0e19c421afc39b531bc6aaaec48e7e7414
Whiteboard: abrt_hash:ae5b954b8d801a0725b872592861ffa6ae262c09;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-01-22 17:21:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Tadej Janež 2023-09-16 10:18:07 UTC 
Version-Release number of selected component:
gjs-1.74.3-1.fc37

Additional info:
reporter:       libreport-2.17.11
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-com.github.tchx84.Flatseal-7445.scope
cmdline:        /usr/bin/gjs /usr/bin/com.github.tchx84.Flatseal
crash_function: slab_allocator_free_chunk
executable:     /usr/bin/gjs-console
journald_cursor: s=49ea523a48bf4399aff2788aad01d93d;i=77522;b=04e984a245ad411f902689083c37b35c;m=1293215b;t=60577170e700c;x=81892503cb69d12d
kernel:         6.4.15-100.fc37.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 slab_allocator_free_chunk at ../glib/gslice.c:1415
 #1 magazine_cache_trim at ../glib/gslice.c:725
 #2 magazine_cache_push_magazine at ../glib/gslice.c:756
 #3 thread_memory_magazine2_unload at ../glib/gslice.c:851
 #4 g_slice_free1 at ../glib/gslice.c:1167
 #5 g_slist_foreach at ../glib/gslist.c:887
 #6 pango_layout_line_unref at ../pango/pango-layout.c:5027
 #8 pango_layout_clear_lines at ../pango/pango-layout.c:3240
 #9 pango_layout_finalize at ../pango/pango-layout.c:256
 #12 gtk_label_get_preferred_layout_size at ../gtk/gtklabel.c:3748
Comment 1 Tadej Janež 2023-09-16 10:18:12 UTC 
Created attachment 1989120 [details]
File: backtrace
Comment 2 Tadej Janež 2023-09-16 10:18:13 UTC 
Created attachment 1989121 [details]
File: core_backtrace
Comment 3 Tadej Janež 2023-09-16 10:18:15 UTC 
Created attachment 1989122 [details]
File: cpuinfo
Comment 4 Tadej Janež 2023-09-16 10:18:16 UTC 
Created attachment 1989123 [details]
File: dso_list
Comment 5 Tadej Janež 2023-09-16 10:18:17 UTC 
Created attachment 1989124 [details]
File: environ
Comment 6 Tadej Janež 2023-09-16 10:18:19 UTC 
Created attachment 1989125 [details]
File: exploitable
Comment 7 Tadej Janež 2023-09-16 10:18:20 UTC 
Created attachment 1989126 [details]
File: limits
Comment 8 Tadej Janež 2023-09-16 10:18:21 UTC 
Created attachment 1989127 [details]
File: maps
Comment 9 Tadej Janež 2023-09-16 10:18:23 UTC 
Created attachment 1989128 [details]
File: mountinfo
Comment 10 Tadej Janež 2023-09-16 10:18:24 UTC 
Created attachment 1989129 [details]
File: open_fds
Comment 11 Tadej Janež 2023-09-16 10:18:26 UTC 
Created attachment 1989130 [details]
File: proc_pid_status
Comment 12 Paul W 2023-10-20 01:30:00 UTC 
Similar problem has been detected:

At the moment of locking the screen using Win-L

reporter:       libreport-2.17.11
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        gjs /home/USERID/.local/share/gnome-shell/extensions/ding/app/ding.js -E -P /home/USERID/.local/share/gnome-shell/extensions/ding/app
crash_function: slab_allocator_free_chunk
executable:     /usr/bin/gjs-console
journald_cursor: s=75cc6aff378d48e5bcec557a18fb5d38;i=26f07;b=1a28e3c9a2cd4a05958608a3bc990e5c;m=1e697d416;t=6081b3cb300e1;x=867cab0b04d300eb
kernel:         6.5.6-100.fc37.x86_64
package:        gjs-1.74.3-2.fc37
reason:         gjs-console killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Aoife Moloney 2023-11-23 01:50:27 UTC 
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 14 Aoife Moloney 2024-01-22 17:21:30 UTC 
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.