Created attachment 1764138 [details]
File: backtrace

Created attachment 1764139 [details]
File: core_backtrace

Created attachment 1764140 [details]
File: cpuinfo

Created attachment 1764141 [details]
File: dso_list

Created attachment 1764142 [details]
File: environ

Created attachment 1764143 [details]
File: limits

Created attachment 1764144 [details]
File: maps

Created attachment 1764145 [details]
File: mountinfo

Created attachment 1764146 [details]
File: open_fds

Created attachment 1764147 [details]
File: proc_pid_status

*** Bug 1940251 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Unlocking session

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: std::default_delete<JS::PersistentRooted<JSFunction*> >::operator()(JS::PersistentRooted<JSFunction*>*) const
executable:     /usr/bin/gnome-shell
journald_cursor: s=88b53de70f6e4202b8c0c696f45e8041;i=b0790;b=25daab5e3e614717bdb4250b752dc8a3;m=49a2a80d5;t=5bdcefe0f84b9;x=f8fb67691be0bb74
kernel:         5.11.6-300.fc34.x86_64
package:        gnome-shell-40.0~rc-1.fc34
reason:         gnome-shell killed by SIGBUS
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

I'm seeing this too, and I see a *lot* of reports that look like the same thing with slightly different but similar backtraces. The backtraces differ in the last/first few frames, but they all seem to have a lot of the same frames starting here:

#4  0x00007f68b71ac6b8 in std::default_delete<JS::PersistentRooted<JSFunction*> >::operator() (this=<optimized out>, __ptr=<optimized out>) at /usr/include/c++/11/bits/unique_ptr.h:85
No locals.
#5  std::default_delete<JS::PersistentRooted<JSObject*> >::operator() (__ptr=<optimized out>, this=<optimized out>) at /usr/include/c++/11/bits/unique_ptr.h:79
No locals.
#6  std::__uniq_ptr_impl<JS::PersistentRooted<JSObject*>, std::default_delete<JS::PersistentRooted<JSObject*> > >::reset (__p=0x0, this=0x559b6e2df198) at /usr/include/c++/11/bits/unique_ptr.h:182
        __old_p = <optimized out>
#7  std::unique_ptr<JS::PersistentRooted<JSObject*>, std::default_delete<JS::PersistentRooted<JSObject*> > >::reset (__p=0x0, this=0x559b6e2df198) at /usr/include/c++/11/bits/unique_ptr.h:456

This is the oldest non-private report, so I'm going to dupe all the others against this.

*** Bug 1940010 has been marked as a duplicate of this bug. ***

*** Bug 1940487 has been marked as a duplicate of this bug. ***

*** Bug 1940439 has been marked as a duplicate of this bug. ***

*** Bug 1940306 has been marked as a duplicate of this bug. ***

*** Bug 1940215 has been marked as a duplicate of this bug. ***

Kalev pointed me to the upstream report for this. The workaround for now is to downgrade gjs to 1.67.2, he has pulled 1.67.3 from the megaupdate for now. For Rawhide I'll see if I can revert the problematic commit until we have a proper fix.

the upstream issue https://gitlab.gnome.org/GNOME/gjs/-/issues/387

yes, I already linked it. See that "Link ID" in my previous comment. :D

https://koji.fedoraproject.org/koji/taskinfo?taskID=64085309 is a Rawhide build with patches to revert https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/585 , as suggested by Philip in the upstream issue. Hopefully that'll work around this on Rawhide till a correct fix is available. For F34 I think it's probably best to just stick with the 1.67.2 downgrade for now.

Similar problem has been detected:

Gnome Shell traced back after resuming from suspended activity

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: JS::Rooted<JSObject*>::Rooted<JSContext*, JS::PersistentRooted<JSObject*>&>
executable:     /usr/bin/gnome-shell
journald_cursor: s=df14766021654958aae3331171dca1f9;i=2f2a6;b=8ff889c3b6a54dd298dcbaaefc663814;m=30883d69e;t=5bdda9abf8426;x=4d8aeb2d01aa489
kernel:         5.11.0-0.rc5.134.bz1651886_3.fc34.x86_64
package:        gnome-shell-40.0~rc-1.fc34
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Note that that merge request fixes another crash, although a bit less problematic, as it's "only" a SIGSEGV happening when you log out.

yeah, I'd rather have a crash on logout than a crash on unlock.

Similar problem has been detected:

Just booted fresh after installing some updates. 
Logged in to gnome, launched a couple of epiphany windows, crash to gdm happened.

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: JS::Rooted<JSObject*>::Rooted<JSContext*, JS::PersistentRooted<JSObject*>&>
dso_list:       /usr/bin/gnome-shell gnome-shell-40.0~rc-1.fc34.x86_64 (Fedora Project) 1615998075
executable:     /usr/bin/gnome-shell
journald_cursor: s=e7668d57c91e4e1c82cd8b80d144fe6c;i=239615;b=4b55bf54c6434c4991afa52eecf45051;m=32afd06;t=5bde6678a5dcb;x=8454ca8f7cbbba1f
kernel:         5.11.7-300.fc34.x86_64
package:        gnome-shell-40.0~rc-1.fc34
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Sorry for the noise, it's the same lock screen issue. I just remembered I locked and unlocked when first logging in to my user account to see if the updates had fixed it. ~10 seconds after, the crash occurred.

Similar problem has been detected:

Recovered from back screen (locked account, for inactivity).

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: JS::Rooted<JSObject*>::Rooted<JSContext*, JS::PersistentRooted<JSObject*>&>
dso_list:       /usr/bin/gnome-shell gnome-shell-40.0~rc-1.fc34.x86_64 (Fedora Project) 1615972465
executable:     /usr/bin/gnome-shell
journald_cursor: s=a8c8031638f842e8819fa0720fb25fad;i=1f52e9;b=7e2440456a634ff297caa7507fc72f66;m=1d73d97f9;t=5bde8cf8da48a;x=4e9d84715df6807b
kernel:         5.11.7-300.fc34.x86_64
package:        gnome-shell-40.0~rc-1.fc34
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

FEDORA-2021-453df8d9ee has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-453df8d9ee

Similar problem has been detected:

Leaving from sleep, just unlocking the session. Crash append just after pressing ENTER with the keyboard.

reporter:       libreport-2.14.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: JS::Rooted<JSObject*>::Rooted<JSContext*, JS::PersistentRooted<JSObject*>&>
executable:     /usr/bin/gnome-shell
journald_cursor: s=a8c8031638f842e8819fa0720fb25fad;i=1f9623;b=7e2440456a634ff297caa7507fc72f66;m=146a70c850;t=5bdfc72a62ace;x=f1d04d5840e43129
kernel:         5.11.7-300.fc34.x86_64
package:        gnome-shell-40.0~rc-1.fc34
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

FEDORA-2021-453df8d9ee has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

*** Bug 1941531 has been marked as a duplicate of this bug. ***

*** Bug 1941281 has been marked as a duplicate of this bug. ***

*** Bug 1940024 has been marked as a duplicate of this bug. ***

*** Bug 1940355 has been marked as a duplicate of this bug. ***