Created attachment 1358022 [details]
File: backtrace

Created attachment 1358023 [details]
File: cgroup

Created attachment 1358024 [details]
File: core_backtrace

Created attachment 1358025 [details]
File: cpuinfo

Created attachment 1358026 [details]
File: dso_list

Created attachment 1358027 [details]
File: environ

Created attachment 1358028 [details]
File: limits

Created attachment 1358029 [details]
File: maps

Created attachment 1358030 [details]
File: mountinfo

Created attachment 1358031 [details]
File: open_fds

Created attachment 1358032 [details]
File: proc_pid_status

Created attachment 1358033 [details]
File: var_log_messages

*** This bug has been marked as a duplicate of bug 1510059 ***

This is not a dupe of 1510059. It's another case of "failed to allocate 18446744072098939136 bytes", which is #1526164 .

*** This bug has been marked as a duplicate of bug 1526164 ***

I'm running Fedora 28 and ABRT pointed me to this bug.

--- Running report_uReport ---
('report_uReport' completed successfully)

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES'
Querying server settings
Retrace server can not be used, because the crash is too large. Try local retracing.
The size of your crash is 1.5 GiB, but the retrace server only accepts crashes smaller or equal to 1.2 GiB.
Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'YES'
Analyzing coredump 'coredump'
Missing build id: libnvidia-glcore.so.390.77
Missing build id: libnvidia-tls.so.390.77
Missing build id: libGLX_nvidia.so.0
Missing build id: libnvidia-egl-wayland.so.1
Missing build id: libnvidia-glsi.so.390.77
Missing build id: libEGL_nvidia.so.0
Coredump references 201 debuginfo files, 7 of them are not installed
Initializing package manager
Setting up repositories
Looking for needed packages in repositories
Packages to download: 5
Downloading 3.05Mb, installed size: 11.93Mb. Continue? 'YES'
Downloading (1 of 5) gdm-debuginfo-3.28.4-1.fc28.x86_64.rpm: 100%
Extracting cpio from /var/tmp/dnf-abrt-j5l_k0ey/updates-debuginfo-31001629c662a347/packages/gdm-debuginfo-3.28.4-1.fc28.x86_64.rpm
Caching files from unpacked.cpio made from gdm-debuginfo-3.28.4-1.fc28.x86_64.rpm
Downloading (2 of 5) pango-debuginfo-1.42.4-1.fc28.x86_64.rpm: 100%
Extracting cpio from /var/tmp/dnf-abrt-j5l_k0ey/updates-debuginfo-31001629c662a347/packages/pango-debuginfo-1.42.4-1.fc28.x86_64.rpm
Caching files from unpacked.cpio made from pango-debuginfo-1.42.4-1.fc28.x86_64.rpm
Downloading (3 of 5) libxcrypt-debuginfo-4.1.2-1.fc28.x86_64.rpm: 100%
Extracting cpio from /var/tmp/dnf-abrt-j5l_k0ey/updates-debuginfo-31001629c662a347/packages/libxcrypt-debuginfo-4.1.2-1.fc28.x86_64.rpm
Caching files from unpacked.cpio made from libxcrypt-debuginfo-4.1.2-1.fc28.x86_64.rpm
Downloading (4 of 5) gnutls-debuginfo-3.6.3-4.fc28.x86_64.rpm: 100%
Extracting cpio from /var/tmp/dnf-abrt-j5l_k0ey/updates-debuginfo-31001629c662a347/packages/gnutls-debuginfo-3.6.3-4.fc28.x86_64.rpm
Caching files from unpacked.cpio made from gnutls-debuginfo-3.6.3-4.fc28.x86_64.rpm
Downloading (5 of 5) gnome-bluetooth-libs-debuginfo-3.28.2-1.fc28.x86_64.rpm: 100%
Extracting cpio from /var/tmp/dnf-abrt-j5l_k0ey/updates-debuginfo-31001629c662a347/packages/gnome-bluetooth-libs-debuginfo-3.28.2-1.fc28.x86_64.rpm
Caching files from unpacked.cpio made from gnome-bluetooth-libs-debuginfo-3.28.2-1.fc28.x86_64.rpm
Removing /var/tmp/abrt-tmp-debuginfo.wcrkuR
All debuginfo files are available
Generating backtrace
Backtrace is generated and saved, 84451 bytes

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
Duplicate bugzilla bug '#1516633' was found
Searching for updates
No updates for this package found

I am often being pointed to this bug.  When must screen locks, and I come back and log on, gnome-shell crashes and restarts.  ABRT points my situation to THIS bug.

Louis, can you post your actual backtrace, and the journal messages from around the time the crash happens? I can't tell what bug you're actually hitting without that info, unfortunately. Thanks!

Hi.  Sorry I overlooked this request.  I get a couple of regular bug reports for old Buzilla ID's.  Here is a crash I got yesterday, and in this particular case it reported:
Duplicate bugzilla bug '#712612' was found

Below is the uReport info:
uReport: BTHASH=70e9c86516626de6e554423cf53b22abb46a5e82
ABRT Server: URL=https://retrace.fedoraproject.org/faf/reports/bthash/70e9c86516626de6e554423cf53b22abb46a5e82

I will attach the backtrace for you.

Created attachment 1486539 [details]
Backtrace and /var/log/messages

This is as generated by ABRT.

Happens often, but not always, on screen lock, on Fedora 29, 30.

Backtrace genereren
Backtrace is too big (579548 bytes), reducing depth to 512
Backtrace is too big (577486 bytes), reducing depth to 256
Backtrace is too big (577486 bytes), reducing depth to 128
Backtrace is too big (577486 bytes), reducing depth to 64
Backtrace wordt gegenereerd en opgeslagen, 55244 bytes

--- Running analyze_BodhiUpdates ---
Zoeken naar vergelijkbare problemen in bugzilla
Duplicate bugzilla bug '#1516633' was found
Searching for updates
No updates for this package found

Happens occasionally here, usually when using GNOME terminal full screen with a couple of tabs. Fedora 32, gnome-shell-3.36.2-2.fc32.x86_64.

Generating backtrace
Backtrace is too big (512137 bytes), reducing depth to 512
Backtrace is too big (510075 bytes), reducing depth to 256
Backtrace is too big (510075 bytes), reducing depth to 128
Backtrace is too big (510075 bytes), reducing depth to 64
Backtrace is generated and saved, 30597 bytes

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
Duplicate bugzilla bug '#1516633' was found
Searching for updates
No updates for this package found

I guess something is messed up here. I got here from trying to report this crash:
https://retrace.fedoraproject.org/faf/reports/2904053/
In my case, it seems to come from some JS code calling st_theme_unload_stylesheet when the screen is being locked, but something about the following style changes fails.
This is new since updating to fedora 32 and happens pretty often when locking the screen or suspending.
My syslog says:
--Mai 11 12:38:28 escher gnome-shell[2311]: **
Mai 11 12:38:28 escher gnome-shell[2311]: St:ERROR:../src/st/st-theme.c:1048:_st_theme_resolve_url: assertion failed: (base_file)
Mai 11 12:38:28 escher gnome-shell[2311]: Bail out! St:ERROR:../src/st/st-theme.c:1048:_st_theme_resolve_url: assertion failed: (base_file)
Mai 11 12:38:28 escher gnome-shell[2311]: == Stack trace for context 0x564a37a41480 ==
Mai 11 12:38:28 escher gnome-shell[2311]: #0   564a38d427d8 i   resource:///org/gnome/shell/ui/extensionSystem.js:107 (2936af068358 @ 467)
Mai 11 12:38:28 escher gnome-shell[2311]: #1   564a38d42748 i   resource:///org/gnome/shell/ui/extensionSystem.js:593 (2936af06a538 @ 15)
Mai 11 12:38:28 escher gnome-shell[2311]: #2   7ffd42f6f5a0 b   self-hosted:266 (2e7975face20 @ 259)
Mai 11 12:38:28 escher gnome-shell[2311]: #3   564a38d426b8 i   resource:///org/gnome/shell/ui/extensionSystem.js:592 (2936af06a4c0 @ 98)
Mai 11 12:38:28 escher gnome-shell[2311]: #4   564a38d42628 i   resource:///org/gnome/shell/ui/extensionSystem.js:610 (2936af06a5b0 @ 82)
Mai 11 12:38:28 escher gnome-shell[2311]: #5   7ffd42f70830 b   self-hosted:1009 (1d8d6269e358 @ 423)
Mai 11 12:38:28 escher gnome-shell[2311]: #6   7ffd42f70930 b   resource:///org/gnome/gjs/modules/core/_signals.js:133 (2e7975fac880 @ 427)
Mai 11 12:38:28 escher gnome-shell[2311]: #7   7ffd42f71850 b   resource:///org/gnome/shell/ui/sessionMode.js:195 (1d8d62624d30 @ 286)
Mai 11 12:38:28 escher gnome-shell[2311]: #8   564a38d423c8 i   resource:///org/gnome/shell/ui/sessionMode.js:156 (1d8d62624b50 @ 40)
Mai 11 12:38:28 escher gnome-shell[2311]: #9   564a38d42310 i   resource:///org/gnome/shell/ui/screenShield.js:571 (1d8d6260fd30 @ 191)
Mai 11 12:38:28 escher gnome-shell[2311]: #10   564a38d42250 i   resource:///org/gnome/shell/ui/screenShield.js:620 (1d8d6260fda8 @ 419)
Mai 11 12:38:28 escher gnome-shell[2311]: #11   564a38d421b8 i   resource:///org/gnome/shell/ui/shellDBus.js:378 (1d8d626158f8 @ 67)
Mai 11 12:38:28 escher gnome-shell[2311]: #12   564a38d420d0 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:371 (2e7975f9c1f0 @ 949)
Mai 11 12:38:28 escher gnome-shell[2311]: #13   564a38d42018 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404 (2e7975f9c3d0 @ 34)
--

When I try to report it via abrt, I get the following output:
Generating backtrace
Backtrace is too big (545384 bytes), reducing depth to 512
Backtrace is too big (543322 bytes), reducing depth to 256
Backtrace is too big (543322 bytes), reducing depth to 128
Backtrace is too big (543322 bytes), reducing depth to 64
Backtrace is generated and saved, 98528 bytes
Looking for similar problems in bugzilla
Duplicate bugzilla bug '#1516633' was found
Searching for updates
No updates for this package found

Followed by the message:
Reporting is disabled because the generated backtrace is of low informational value.
So I manually followed the bugzilla ID from the log to end up here, but I guess this used to be a completely unrelated bug.
I couldn't find anything else that seemed more related, so maybe we should open a new issue for this?

Niko: it's not "messed up", exactly, it's just a sort of limitation of how the crash report system works: it tries to group together similar backtraces, so it gets tripped up when different bugs trigger similar backtraces for some reason, as here. It'd be great if you can file a new bug with your javascript trace and any other relevant surrounding logs and config details. Thanks!

Thanks for the info, I opened a new bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1834727