Cider crashing after being left open for some time after latest release

[tannerellen]

Preflight Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.
• I have confirmed that no support FAQ resolves my issue.
• I have checked that the correct behavior occurs on Apple Music Web (if applicable).
• I have verified that my issue is with a supported version and that it is with the desktop app (Support for other areas can be found in our Discord / on the appropriate repo).

How did you download Cider?

itch.io

App Information

{"buildInfo":{"version":"2.6.1.1","commit":"e150895cb86fee459d8f0e26782b730d3e78650c","buildDate":"1738315887947","changelogUrl":"2.6.0-release"},"clientInfo":{"client":"genten","env":"production","arch":"x64","platform":"linux","platformFriendly":"Linux","build":"desktop","clientVersion":"2.0.3","capi":"w2i02ct80s75kym5ak51ns27"}}

Operating System

Linux

OS Version

Arch - Kernel 6.13.1-arch1-1

How would you describe your issue?

Backend (macOS/Linux), Frontend

Commit Hash

No response

Describe the Bug

After the latest release if I leave Cider running it will often crash while my computer sleeps and I come back to it. This did not happen before.

I am left with a message that says "Error: /am/--ozone-platform=wayland not found.".

If I click the button that says "Go Home" It will take me back to the home screen but if I try and do anything like play a song Cider will exit (I'm assuming from a crash).

This has never happened on any of the previous releases.

Steps to Reproduce

Open Cider play a song. Pause the song. Leave cider open and let your computer sleep. Wait some time, then on returning try and access Cider to play as song.

Anything else?

[coredev-uk]

This issue has been identified and rectified on the current commit. You should expect a Taproom experimental release with a fix soon.
It was just a case where the app is being opened with args and they are being parsed as protocol routes.

[tannerellen]

This issue has been identified and rectified on the current commit. You should expect a Taproom experimental release with a fix soon. It was just a case where the app is being opened with args and they are being parsed as protocol routes.

Awesome, thanks for the heads up I just installed the experimental release so hopefully everything will be all good. I'll reopen if the bug still happens but seems like I should be good.

[tannerellen]

I am reopening this issue because It is still happening for me on the current experimental release on taproom. It doesn't occur as frequently but every once in a while I am still getting the message then accompanied by a cider crash where I have to relaunch.

Generally happens after the app has been running for a long time. I have had it happen mostly after leaving my computer unattended for a long time (like overnight) and then waking it from sleep. But it has also happened during active usage too.

[coredev-uk]

What message shows in the window? Is it the same as before?

[tannerellen]

What message shows in the window? Is it the same as before?

Yeah, exact same as before.

[tannerellen]

Actually I am a little bit confused though because it looks like my build info is the same as when I was using the stable version...

{"buildInfo":{"version":"2.6.1.1","commit":"e150895cb86fee459d8f0e26782b730d3e78650c","buildDate":"1738315887947","changelogUrl":"2.6.0-release"},"clientInfo":{"client":"genten","env":"production","arch":"x64","platform":"linux","platformFriendly":"Linux","build":"desktop","clientVersion":"2.0.3","capi":"dld7vsrbja5r8cyuhe2vj4qm"}}

Shouldn't that be different if I'm using the experimental build?

[coredev-uk]

That commit was done before the fix I made, so not sure if you are on the right build or it could be the case that the SPA you are using does not contain the fix.

[cider-collective]

Hello again!

We've noticed that you haven't replied in a while. Unfortunately, our team isn't always able to address issues as quickly as we'd like. To help us assist you more efficiently, please provide the following information:

1. Ensure your client is as up-to-date as possible. You can do this by using the experimental release on Taproom (if available) and the PTB release through the in-app updater.
2. Let us know if the issue is still present. If it is, please provide the version you're using and mention any changes you've noticed since reporting the issue.

This information will help us identify whether the issue has already been resolved.

Please try to update us within the next 20 days; otherwise, we will close this issue.

Thanks for your help! 😃

[tannerellen]

I’m not experiencing this any longer so it’s been fixed. I’ll close.