I have also experienced a similar issue; however, for the times I've had a game crash with an update available in the background... the update was for the same game I was playing.
So, it may be that any queued update waiting to start in the background leads to the crash.
Your system information
Steam Settings => Downloads
Nothing extracted yet.
This is a report for "Steam for Linux" but this morning I was told the same thing happens in the client for Windows!
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs] Unfortunately none. This problem happened yesterday. The youngest log is from August 3rd.Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Last night I was playing "Mad Max". While I was playing it, a new update for "Titan Quest 2" appeared and "Mad Max" crashed. I had to kill its process using killall in order to close it, nothing else would help. After that I ran "MM" again but it crashed in the menu.
After I allowed "TQ2" to update, the crashes stopped.
This isn't the first such a crash happens when another game has an update waiting. The first two times it happened I thought I had pressed something that I shouldn't but after "Mad Max" (the native Linux version) crashed while I was hanging at a balloon without touching any keys, I'm pretty sure the cause of these crashes is when an update for a game is released and is waiting to be downloaded.
Ever since I bought "Mad Max" (2015 or 2016 - I don't remember when exactly) I've never had a single crash of the game, until now.
I've set the client not to download/update anything while I'm playing a game, so thus must be a bug in the steam client.
What happened: while playing a game an update for another game in the library is released and the currently played game crashed.
What shouldn't happen: currently played game shouldn't crash when an update for another game appears.
Steps for reproducing this issue:
P.S. The user Brynvagn said he's noticed the same behavior in the topic I posted in the steam community: https://steamcommunity.com/app/221410/discussions/0/802322896293800767/