#[0.0.8-rc2] Linux - Intermittent Crash to Desktop on Cut/Copy

19 messages · Page 1 of 1 (latest)

left dragon
#

It's not every time, but it's often enough to become an issue if I'm not saving often. When I go to cut/copy either buildings or platforms the game will freeze for a few seconds then crash to desktop. I notice it happening more frequently if I'm switching windows (alt+tab) a lot, or if I'm idling the game while reading Discord, or something else, etc..

Operating System: openSUSE Tumbleweed 20240819
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.5-1-default (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XTX
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D70
System Version: 1.0

Steam Launch Options: SDL_VIDEODRIVER=wayland %command%

📎 Player.log
fathom patio
#

Hey, could you check if this also happens with 0.0.7 (the default branch)?

left dragon
#

To my memory this never happened on 0.0.7

It was completely stable in all in-game actions. However I will test if using the Steam Launch option for Wayland causes any changes. However, I don't believe the launch option was available according to this post #1274249453259194368 message

#

My pc is off at the moment. I'll test tomorrow.

uncut briarBOT
#

👍 Your bug report is in review. Our team is currently investigating.

left dragon
#

As expected I could not get the game to run on 0.0.7 with the SDL_VIDEODRIVER=wayland %command% Steam Launch Option.

However, I did do some iterative testing in 0.0.8-rc2 to narrow down when the crash was occurring, and was successful in causing the crash on demand.

Steps to Reproduce:

Version: 0.0.8-rc2
Steam Launch Options: SDL_VIDEODRIVER=wayland %command%

  1. Clear System Clipboard (Optional, but helps with consistency)
  2. Start Game and Load Save
  3. Copy/Cut any object. Either at Building or at Platform scale. (do not need to paste)
  4. Switch to another program and Copy some data (text, image, etc..)
  5. Switch back to the Game and Copy/Cut any object at Platform scale (not Buildings, they are safe)

If you happen to Copy/Cut a Platform after Copy/Cut some Buildings the crash will still happen.

__ __

Looks like something wonky is happening with the interaction between the Game and System Clipboard operations when running Wayland. On 0.0.7 with empty launch options this crashing never happens.

Hope this helps!

river venture
#

I will test shortly

#

I can confirm this, though I should note it doesn't happen with the --force-wayland option

left dragon
#

How are you using the --force-wayland option? By itself? or before/after the %command%?

river venture
#

SDL_VIDEODRIVER=wayland %command% crashes as above, but %command% --force-wayland does not

#

And just for clarity, neither does %command% -force-wayland

left dragon
#

Also, all the reference material I've seen in regards to the command flag show only a single dash, not double dash in front. So I wasn't able to test that earlier.

#

and the single dash version crashes the game on focus switch

river venture
#

That I still cannot reproduce, no matter how many times it's stated to be the case

left dragon
#

Just tested, neither the single or double dash --force-wayland actually initializes wayland. It's still on XWayland.

river venture
#

Either way, wayland support in Unity is still considered experimental

left dragon
#

Lol, I was about to add my log too. I forgot in the reproduction post. Here's mine for comparison.

📎 Player.log
river venture
#

Personally, I believe this to be a Unity problem moreso than a Shapez2 problem