UPD: after update to 1595290790 version Steam client worked a little longer but ended up crashing with the same error:

***** OUT OF MEMORY! attempted allocation size: 1714434623 ****
/data/src/tier0/memstd.cpp (2448) : Fatal Assertion Failed: OUT OF MEMORY
/data/src/tier0/memstd.cpp (2448) : Fatal Assertion Failed: OUT OF MEMORY
/data/src/tier0/memstd.cpp (2448) : Fatal assert failed: /data/src/tier0/memstd.cpp, line 2448.  Application exiting.

/data/src/tier0/memstd.cpp (2448) : Fatal assert failed: /data/src/tier0/memstd.cpp, line 2448.  Application exiting.

Installing breakpad exception handler for appid(steam)/version(1595290790)
assert_20200721135616_185.dmp[138309]: Uploading dump (out-of-process)
/tmp/dumps/assert_20200721135616_185.dmp
_ExitOnFatalAssert
[mikhail@localhost ~]$ assert_20200721135616_185.dmp[138309]: Finished uploading minidump (out-of-process): success = yes
assert_20200721135616_185.dmp[138309]: response: CrashID=bp-3f20178b-6e37-4c0f-973f-3df892200721
assert_20200721135616_185.dmp[138309]: file ''/tmp/dumps/assert_20200721135616_185.dmp'', upload yes: ''CrashID=bp-3f20178b-6e37-4c0f-973f-3df892200721''

Full version here
mikhail_log.txt
assert_20200721135616_185.zip

UPD2: It coincided with the end time processing shaders for "Rise of Tomb Raider".

Demonstration 1: https://youtu.be/Yszs_VCgDTU
Demonstration 2: https://youtu.be/9fdql92zmD8

Having the same issue here on Arch and Fedora 32

Any news on this? I literally can't keep Steam open for more than a few minutes, and by extension, any games I have purchased.

Ditto for launching Big Picture on Arch on an RX550 4GB (the most recent change on the system aside from underhanded updates).

Also, I couldn't launch the game "Rise of Tomb Raider" itself because when I launch the game steam client starts shader processing which is ended with a crash with "OUT OF MEMORY" message.
Demonstration: https://youtu.be/aMlNmixoQbA?t=330

I also have the same issue with arch.

I disabled the "Enable shader pre-caching" option and it seems to be stable now.

I'm running at Manjaro

The above does not replicate on setup mentioned earlier with Mesa 20.2.

Found yet another game that causes steam client crash. Before starting Borderlands 3 steam client tries processing shaders very long time and it ends with a crash.

Proton: Upgrading prefix from 5.0-1 to 5.13-1 (/home/mikhail/.local/share/Steam/steamapps/compatdata/397540/)
esync: up and running.
wine: configuration in L"/home/mikhail/.local/share/Steam/steamapps/compatdata/397540/pfx" has been updated.
GameAction [AppID 397540, ActionID 6] : LaunchApp changed task to SynchronizingCloud with ""
GameAction [AppID 397540, ActionID 6] : LaunchApp changed task to ProcessingShaderCache with ""
***** OUT OF MEMORY! attempted allocation size: 942815292 ****
/data/src/tier0/memstd.cpp (2448) : Fatal Assertion Failed: OUT OF MEMORY
/data/src/tier0/memstd.cpp (2448) : Fatal Assertion Failed: OUT OF MEMORY
/data/src/tier0/memstd.cpp (2448) : Fatal assert failed: /data/src/tier0/memstd.cpp, line 2448.  Application exiting.

/data/src/tier0/memstd.cpp (2448) : Fatal assert failed: /data/src/tier0/memstd.cpp, line 2448.  Application exiting.

Installing breakpad exception handler for appid(steam)/version(1602795778)
crash_20201017205021_252.dmp[243553]: Uploading dump (out-of-process)
/tmp/dumps/crash_20201017205021_252.dmp
_ExitOnFatalAssert
[mikhail@localhost ~]$ crash_20201017205021_252.dmp[243553]: Finished uploading minidump (out-of-process): success = yes
crash_20201017205021_252.dmp[243553]: response: CrashID=bp-91d17ae7-e46a-4253-9cce-569182201017
crash_20201017205021_252.dmp[243553]: file ''/tmp/dumps/crash_20201017205021_252.dmp'', upload yes: ''CrashID=bp-91d17ae7-e46a-4253-9cce-569182201017''

mikhail_log.txt
crash_20201017205021_252.zip

I don't know could fossilize_replay use AMDVLK driver, but with installed AMDVLK driver steam client crashed too.
mikhail_log.txt
assert_20201017223209_312.zip

The same problem started to happen for my yesterday on Ubuntu 20.04LTS, Steam have been stable and working for years for me so this came out of nowhere.

And I cannot even disable the precaching of the shader caches because Steam segfaults the very second I click the button to turn it off.

Is there any way to disable the shader caches manually by editing some config file?

The last error in the terminal is
***** OUT OF MEMORY! attempted allocation size: 1664312640 ****

Which should not happen since I have 16GB free at the time of the crash.

error.log

The same problem started to happen for my yesterday on Ubuntu 20.04LTS, Steam have been stable and working for years for me so this came out of nowhere.

Would you be able to provide your apt or dpkg installation log, if that started happening since the last time you've updated packages on your system?

Here is the apt history file
history.log

OK so I tried the nuclear option: "rm -rf ~/.local/share/Steam/steamapps/shadercache" and after starting Steam again it downloaded and processed a lot of shaders but it never segfaulted and now it's finished and still standing so it looks like one of the caches had entered some state that caused Steam of fossilize to crash before.

Happens to me after system updates.

Start-Date: 2020-12-15  13:21:24
Commandline: apt upgrade --fix-missing
Requested-By: danet (1000)
Upgrade: signon-plugin-password:amd64 (8.59+17.10.20170606-0ubuntu2, 8.59+17.10.20170606-0ubuntu2.20.10.1), libsignon-qt5-1:amd64 (8.59+17.10.20170606-0ubuntu2, 8.59+17.10.20170606-0ubuntu2.20.10.1), signond:amd64 (8.59+17.10.20170606-0ubuntu2, 8.59+17.10.20170606-0ubuntu2.20.10.1), libsignon-plugins-common1:amd64 (8.59+17.10.20170606-0ubuntu2, 8.59+17.10.20170606-0ubuntu2.20.10.1), apport:amd64 (2.20.11-0ubuntu50.2, 2.20.11-0ubuntu50.3), libinput-bin:amd64 (1.16.2-1, 1.16.2-1ubuntu0.1), ubuntu-drivers-common:amd64 (1:0.8.6.1, 1:0.8.6.2), python3-apport:amd64 (2.20.11-0ubuntu50.2, 2.20.11-0ubuntu50.3), apport-kde:amd64 (2.20.11-0ubuntu50.2, 2.20.11-0ubuntu50.3), python3-problem-report:amd64 (2.20.11-0ubuntu50.2, 2.20.11-0ubuntu50.3), libsignon-extension1:amd64 (8.59+17.10.20170606-0ubuntu2, 8.59+17.10.20170606-0ubuntu2.20.10.1), libinput10:amd64 (1.16.2-1, 1.16.2-1ubuntu0.1), libevdev2:amd64 (1.9.1+dfsg-1, 1.9.1+dfsg-1ubuntu0.1)
End-Date: 2020-12-15  13:21:29

Start-Date: 2020-12-15  13:24:11
Commandline: packagekit role='update-packages'
Requested-By: danet (1000)
Upgrade: linux-firmware:amd64 (1.192, 1.193)
End-Date: 2020-12-15  13:28:14

Start-Date: 2020-12-16  18:58:10
Commandline: packagekit role='update-packages'
Requested-By: danet (1000)
Upgrade: libmagickcore-6.q16-6-extra:amd64 (8:6.9.10.23+dfsg-2.1ubuntu13, 8:6.9.10.23+dfsg-2.1ubuntu13.1), imagemagick:amd64 (8:6.9.10.23+dfsg-2.1ubuntu13, 8:6.9.10.23+dfsg-2.1ubuntu13.1), libmagickwand-6.q16-6:amd64 (8:6.9.10.23+dfsg-2.1ubuntu13, 8:6.9.10.23+dfsg-2.1ubuntu13.1), imagemagick-6.q16:amd64 (8:6.9.10.23+dfsg-2.1ubuntu13, 8:6.9.10.23+dfsg-2.1ubuntu13.1), firefox-locale-en:amd64 (83.0+build2-0ubuntu0.20.10.1, 84.0+build3-0ubuntu0.20.10.1), libmagickcore-6.q16-6:amd64 (8:6.9.10.23+dfsg-2.1ubuntu13, 8:6.9.10.23+dfsg-2.1ubuntu13.1), firefox:amd64 (83.0+build2-0ubuntu0.20.10.1, 84.0+build3-0ubuntu0.20.10.1), imagemagick-6-common:amd64 (8:6.9.10.23+dfsg-2.1ubuntu13, 8:6.9.10.23+dfsg-2.1ubuntu13.1)
End-Date: 2020-12-16  18:58:17

Start-Date: 2020-12-17  10:58:54
Commandline: packagekit role='update-packages'
Requested-By: danet (1000)
Install: linux-image-5.9.15-xanmod1:amd64 (5.9.15-xanmod1-0~git20201216.d99be53), linux-headers-5.9.15-xanmod1:amd64 (5.9.15-xanmod1-0~git20201216.d99be53)
Upgrade: libegl1-mesa-dev:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libegl-mesa0:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libglapi-mesa:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libglapi-mesa:i386 (20.3.0~kisak4~g, 20.3.1~kisak1~g), mesa-common-dev:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), linux-xanmod:amd64 (5.9.14-xanmod1-0, 5.9.15-xanmod1-0), libosmesa6-dev:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libxatracker2:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libgbm1:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libgbm1:i386 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libgl1-mesa-dev:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libgl1-mesa-dri:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libgl1-mesa-dri:i386 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libosmesa6:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libosmesa6:i386 (20.3.0~kisak4~g, 20.3.1~kisak1~g), code:amd64 (1.52.0-1607640828, 1.52.1-1608136922), libgl1-mesa-glx:i386 (20.3.0~kisak4~g, 20.3.1~kisak1~g), mesa-vdpau-drivers:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), mesa-vdpau-drivers:i386 (20.3.0~kisak4~g, 20.3.1~kisak1~g), mesa-vulkan-drivers:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), mesa-vulkan-drivers:i386 (20.3.0~kisak4~g, 20.3.1~kisak1~g), mesa-va-drivers:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), mesa-va-drivers:i386 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libglx-mesa0:amd64 (20.3.0~kisak4~g, 20.3.1~kisak1~g), libglx-mesa0:i386 (20.3.0~kisak4~g, 20.3.1~kisak1~g)
End-Date: 2020-12-17  10:59:39

This issue seems to intermittently disappear and reappear. It had solved itself for a few months, but now it's back full force on Arch.

Perhaps there are a number of separate issues conflated here - does it happen more often when trying to switch to Big Picture?

Happens without Big Picture regulary

And back when I had the same problems (that I solved by simply delete the cache) I never even used Big Picture and Steam crashed every single time it started.

happens for me regularly since about 2 weeks ago, never used big picture, and so far i've notice it crashing a few times about 10 minutes into playing "Valheim" (natively, not Proton), and after about 2 hours into "Horizon: Zero Dawn" (proton, might also not be related because there i haven't checked for the OOM message yet), not noticed it with any other games (i regularly play Warframe and Elite:Dangerous for hours, both on Proton) yet, but i've noticed sometimes i leave steam running over night and the next morning it's gone, might be related (or just due to it not surviving my PC suspending, not sure).

just nuked the shadercache directories in all of my libraries, and disabled "background processing" (i suspect it might just run into weird driver issues trying to fossilize shaders from one game while another one thinks it's got the vulkan context to itself or something)

for the record since this used to be flagged for fedora: i'm on void linux. and the gpu in question (might be important for fossilize): gtx 980 ti

Getting the same issue on NixOS
Issue #7836

I started to get the same problem on Ubuntu. Never had this issue before, but since a couple of days my steam client randomly crashes with that "OUT OF MEMORY" exception. There is no further information in the console, though.

Latest beta may have a fix for this:
https://steamcommunity.com/groups/SteamClientBeta/announcements/detail/2972920842735688245

I should add that I'm on the beta branch and usually I have around 22-24 gigs free of ram and 12 cores/24 threads, but fossilize does not use them all, so, in theory, the RAM should be sufficient. Unfortunately the crashes happen rather unexpected, so I don't know how much RAM was being used. I'll try to monitor that.

Still occurs in this case, which makes me lean towards stating that it might be multiple distinct problems with similar symptoms.

Hardware (primarily GPU) and driver stack (Mesa, proprietary?) outlines would be useful, when providing reports in this issue.

So far, since the update, it ran stable for me while it usually crashed shortly after logging into the desktop. So at least one problem seems to be fixed. But the beta changelog also tells us that this is only a first fix in a series of proposed fixes. But I don't want to meet trouble halfway, usually, when I wrote it's stable, it would start to crash again the next day.

The issue still happens even with latest steam beta.

Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
***** OUT OF MEMORY! attempted allocation size: 201326592 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal assert; application exiting
src/tier0/memstd.cpp (2489) : Fatal assert; application exiting
Installing breakpad exception handler for appid(steam)/version(1625098228)
assert_20210701101131_244.dmp[19656]: Uploading dump (out-of-process)
/tmp/dumps/assert_20210701101131_244.dmp
_ExitOnFatalAssert
[mikhail@fedora ~]$ assert_20210701101131_244.dmp[19656]: Finished uploading minidump (out-of-process): success = yes
assert_20210701101131_244.dmp[19656]: response: CrashID=bp-59af51a0-78fe-45c2-8920-528c52210630
assert_20210701101131_244.dmp[19656]: file ''/tmp/dumps/assert_20210701101131_244.dmp'', upload yes: ''CrashID=bp-59af51a0-78fe-45c2-8920-528c52210630''

mikhail_log.txt
assert_20210701101131_244.zip

Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
***** OUT OF MEMORY! attempted allocation size: 2097152 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal assert; application exiting
src/tier0/memstd.cpp (2489) : Fatal assert; application exiting
Installing breakpad exception handler for appid(steam)/version(1625098228)
Installing breakpad exception handler for appid(steam)/version(1625098228)
***** OUT OF MEMORY! attempted allocation size: 2097152 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
***** OUT OF MEMORY! attempted allocation size: 1048576 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
***** OUT OF MEMORY! attempted allocation size: 1572864 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
***** OUT OF MEMORY! attempted allocation size: 2097152 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
***** OUT OF MEMORY! attempted allocation size: 2097152 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
***** OUT OF MEMORY! attempted allocation size: 2097152 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
Installing breakpad exception handler for appid(steam)/version(1625098228)
***** OUT OF MEMORY! attempted allocation size: 2097152 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
crash_20210701205809_679.dmp[204547]: Uploading dump (out-of-process)
/tmp/dumps/crash_20210701205809_679.dmp
_ExitOnFatalAssert
crash_20210701205809_679.dmp[204547]: Finished uploading minidump (out-of-process): success = yes
crash_20210701205809_679.dmp[204547]: response: CrashID=bp-bee10dc3-0b8d-431a-9eed-a2ff92210701
crash_20210701205809_679.dmp[204547]: file ''/tmp/dumps/crash_20210701205809_679.dmp'', upload yes: ''CrashID=bp-bee10dc3-0b8d-431a-9eed-a2ff92210701''
[mikhail@fedora ~]$ 

mikhail_log.txt
crash_20210701205809_679.zip

Installing breakpad exception handler for appid(steam)/version(1625258093)
Installing breakpad exception handler for appid(steam)/version(1625258093)
Installing breakpad exception handler for appid(steam)/version(1625258093)
Installing breakpad exception handler for appid(steam)/version(1625258093)
***** OUT OF MEMORY! attempted allocation size: 201326592 ****
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal Assertion Failed: OUT OF MEMORY
src/tier0/memstd.cpp (2489) : Fatal assert; application exiting
src/tier0/memstd.cpp (2489) : Fatal assert; application exiting
Installing breakpad exception handler for appid(steam)/version(1625258093)
Installing breakpad exception handler for appid(steam)/version(1625258093)
Installing breakpad exception handler for appid(steam)/version(1625258093)
Installing breakpad exception handler for appid(steam)/version(1625258093)
assert_20210703111253_345.dmp[11456]: Uploading dump (out-of-process)
/tmp/dumps/assert_20210703111253_345.dmp
_ExitOnFatalAssert
[mikhail@fedora ~]$ assert_20210703111253_345.dmp[11456]: Finished uploading minidump (out-of-process): success = yes
assert_20210703111253_345.dmp[11456]: response: CrashID=bp-e62be57d-724b-4c8b-b09b-caf2a2210702
assert_20210703111253_345.dmp[11456]: file ''/tmp/dumps/assert_20210703111253_345.dmp'', upload yes: ''CrashID=bp-e62be57d-724b-4c8b-b09b-caf2a2210702''

mikhail_log.txt
assert_20210703111253_345.zip

This started happening on my Gentoo Linux system today for the first time. Going back from BETA to official didn't fix it, removing the shader cache completely didn't solve it. Disabling the shader cache made Steam work again

soooo some time in between i reenabled the shader cache and it worked for a month or two, then started crashing again due to the same issue...

took the opportunity of watching it happen, it immediately tries to allocate more (both system and video) RAM than available, fails, then either dies to "OUT OF MEMORY" or sometimes even tries to address said ram it didn't get to allocate, segfaulting as a result.

pretty sure fossilize is being fed either corrupted or too much data without sanity checks (and steam seems to just die as a result of that instead of handling it gracefully)

@Plagman
How to suggest steam developers to implement shader compilation control.

1. Auto mode.
2. Manual mode. Choosing which to compile and choosing the order.

Due to recently having to temporarily switch from linux-hardened to linux-zen, because of a debugfs bug in Mesa, I've managed to run BP and Remote Play successfully on Polaris/AMDGPU, so if it's not too presumptious of me to ask people affected by this issue: could you remark which kernel you're using when this manifests?

Due to recently having to temporarily switch from linux-hardened to linux-zen, because of a debugfs bug in Mesa, I've managed to run BP and Remote Play successfully, so if it's not too presumptious of me to ask people affected by this issue: could you remark which kernel you're using when this manifests?

I've always been using either the latest stable generic kernel or the LTS kernel

I get this bug as well. Running Pop!_OS 21.04 (Kernel version 5.13.0). Steam runs fine for at least a few hours and then crashes, usually while a game is running in Proton with the OUT OF MEMORY! error in the log.

usually while a game is running in Proton with the OUT OF MEMORY! error in the log

Yep, can confirm that, and it usally insta-kills the game with it (probably because games receive awkward data from the Steam API, games without Steam API seem to survive most of the time), no chance to save your progress. Argh!

But this is one instance of two I'm seeing:

1. This one is crashing while in game, and I didn't find out what Steam is actually doing in the background when it happens.
2. The other is crashing while the system is idle, and this seem to almost always result from a Steam client update check.

Is this bug caused by steam client exhausting its 32bit address space? I get steam crashes one 10 minutes or so, it's very annoying.

If this is just steam using more than 4G of memory, instead of any actual bugs, then a 64bit steam client should fix this? There is already a 64bit Mac client IIUC, would it be difficult to also have one for Linux?

Is this bug caused by steam client exhausting its 32bit address space? I get steam crashes one 10 minutes or so, it's very annoying.

Last time I checked, it was a 32-bit process that crashed...

Same here on Ubuntu 22.04, after kernel's update (now 5.15.30, prev was 5.15.27).
Laptop: MSI
CPU: AMD Ryzen 7 4000 series
GPU: AMD Radeon RX 5600m

i have the same issue.
GPU is 5700xt, driver is regular amdgpu, OS is basically just a clean latest debian without any changes.
happens on both mainline kernel and liquorix, both latest.
happens both in the latest beta and in not beta.
clearing the shader cache helped for like 10 minutes, until shaders for Risk Of Rain 2 finished downloading, crashing steam.
i seem to have solved the issue by clearing the shader cache again, the disabling both options in shader caching.

this has obviously removed all shaders from my downloads and now the next thing is a payday update, notoriously large so i don't know if it will crash at the end but it hasn't crashed since.

I am unsure whether my issue is the exact same bug. But since Steam client version 1695085405 I am experiencing random, full-scope system freezes on Manjaro / Arch (Kernel 6.1.49-1). I have not found any clue on what functionality of the Steam client is forcing this behavior. It happens primarily when the Steam client is idling or when using the chat functionality. I did not have any issue when playing DOTA.

dmesg result:

[  180.122233] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/[email protected]/app.slice/[email protected],task=fossilize_repla,pid=4985,uid=1000
[  180.122242] Out of memory: Killed process 4985 (fossilize_repla) total-vm:10416544kB, anon-rss:9757564kB, file-rss:0kB, shmem-rss:576kB, UID:1000 pgtables:19444kB oom_score_adj:200
[  183.307695] traps: Chrome_IOThread[2011] trap invalid opcode ip:7f8989bdb794 sp:7f897ff2bcd0 error:0 in libcef.so[7f89872ef000+7770000]

Let me know if you need anything else for debugging.