[1.0.3-rc3] [Linux] Game crashes after several hours

[terse dome]

I'm reaching the endgame of the Classic Regular game. As in I've reached the last milestone but I want to fully unlock the last item in the shop. But it is really hard to finish it because the game usually crashes after a couple of hours. I can't pinpoint a specific action that causes the crash.

This might just be due to the amount of machines I've running (1.81 million) but it is weird that it is fine for hours, so maybe a memory leak?

When the game freezes my entire system is locked and I need a hard reset on my pc. I can understand if the game has difficulties at this stage of the game, but I rather see it only crash the game and not my entire pc 🙂

I'm running on Linux Mint 22.3 with Linux kernel 6.14.0.37-generic

[mortal kelp]

Thank you for reporting this bug! Our team will review your report soon.
Feel free to add more details in follow-up messages — we're also scanning for duplicate reports automatically now.
📨 There are currently 23 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.

📋 Log files help us investigate issues. You can find yours here:
• Windows: %USERPROFILE%\AppData\LocalLow\tobspr Games\shapez 2\Player.log

[mortal kelp]

💾 Untitled Savegame

Started in

1.0.2-rc1

Last played in

1.0.3-rc3

Scenario

Classic - Regular

Seed

23645

Research

100%

Buildings

1,815,349

Completed

Yes

[mortal kelp]

📋 Log File Analysis

Log Analysis (Player.log):

1. Assertion Failed: An assertion in steamnetworkingsockets_lowlevel.cpp at line 2764 failed because the SteamNetworkingSockets service thread waited 1375ms for a lock.

1. [SPZ2-1987] — 👀 72% similar

Rare display crash condition
Done • Priority: Medium • Fix: OLD Early Access • Resolution: Won't Fix

Player experienced a rare system crash after approximately 40 minutes of playtime where all displays went dark and sound output looped. The crash required a hard PC reboot via power button. A second occurrence happened at 2.2 hours of playtime with similar symptoms but game audio continued normally. The issue appears to be system-specific as it also occurs in other games like Victoria 3. Player attempted fixes including disabling fullscreen optimizations, updating graphics drivers, and switch...

2. [SPZ2-5916] — 👀 45% similar

Multiple failed assertion notifications are displayed when loading a specific save with 540K machines.
To Do • Priority: High • Fix: Post 1.0

Loading a savegame with 540K machines triggers over 20 failed assertion notifications in the console log. The issue is caused by a map deserialization order problem where structure states are deserialized before all connected structures are placed, leading to incorrect free space calculations between structures. Because saving is multithreaded, serialization order is nondeterministic, so the bug does not reproduce consistently across builds. The assertions only appear in non-release builds, a...

3. [SPZ2-2932] — 👀 38% similar

Game hangs on shutdown
Done • Priority: Medium • Fix: 4 - Early Access • Resolution: Won't Fix

shapez 2 hangs approximately half the time during shutdown, whether closed via the window button or Exit to Desktop. The issue started recently and correlates with choppy network conditions. A console message briefly mentioning "No Socket" was observed, suggesting a network-related cause. The expected behavior is that the game sends final analytics network requests on quit, which can stall if the network is slow. The issue appears tied to network latency or instability rather than a game logi...
💬 Threads: Game freezes when Quitting

4. [SPZ2-3839] — 👀 30% similar

Save and following "Quit to Desktop"/"Back to Menue" always shows "Quit without saving"
Done • Priority: Medium • Fix: Dimension Update [0.1.0] • Resolution: Done

After saving a Savegame in shapez 2 with 1.34 million Structures, the user no longer has enough time to quit the game without triggering the "Quit without saving?" dialog. The save process takes between 8.5 and 9.5 seconds, but the timer that checks if the player saved recently was set to only 10 seconds instead of the intended 10 minutes. This affects large Savegames on Linux with Steam Cloud disabled. The issue was fixed by increasing the timer from 10 seconds to 120 seconds (2 minutes), th...
💬 Threads: Save and following "Quit to Desktop"/"Ba

5. [SPZ2-1900] — 👀 28% similar

"Assertion failed" console error on first auto save (on laptop)
Done • Priority: Low • Fix: 2 - Demo • Resolution: Duplicate

An "Assertion failed" console error appears on the first auto save when playing on a low-end laptop. The issue occurs after starting a fresh game and placing Conveyor Belts to unlock the first Milestone. The log shows a ServicesInitializationException due to Unity Services failing to initialize because the project is not linked to a Unity project ID. A memory leak with 264 unfreed allocations was also detected. The player was unable to reproduce the issue consistently.

Found 5 similar reports • Searched 3,719 reports • Use /check-duplicates to recheck

[terse dome]

I also have a Player-prev. I don't know if it is needed

[mortal kelp]

📋 Log File Analysis

Thanks for attaching your log file — no errors have been found at a first glance.

[dusk jolt]

idk if its the same issue but try switching to vulkan, it fixed the issue for me

[silent prawn]

Thanks for reporting this issue.
Can you try the following:

1. Try verifying the files.
2. Add the following to the launch options: --disable-store-sdk

[terse dome]

All files where successfully validated. I'll try the launch option after work

[mortal kelp]

✅ Thank you for providing further information, our team will have a look again!

[terse dome]

I got sick so this response took some time. I tried the launch option but that did not fix the issue. Right after an auto-save the game crashed again

[mortal kelp]

✅ Thank you for providing further information, our team will have a look again!

[mortal kelp]

📋 Log File Analysis

Thanks for attaching your log file — no errors have been found at a first glance.

[silent prawn]

Does it still crash if you use proton?

[terse dome]

I'll try it out today

[mortal kelp]

✅ Thank you for providing further information, our team will have a look again!

[silent prawn]

Thanks 🙂

[terse dome]

I've been playing for about 4-5 hours now on Proton 11.0 (beta) and it runs very smoothly so far

[mortal kelp]

✅ Thank you for providing further information, our team will have a look again!

[terse dome]

In the end I've been playing for more then 6 hours when I ran into a crash. But I don't think it has anything to do with the original problem anymore

[mortal kelp]

📋 Log File Analysis

Thanks for attaching your log file — no errors have been found at a first glance.