Unexpected restart of RoonServer with exit code 134 (ref#ADR16E) [Ticket In]

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· RoonServer exitcode 134: unexpected restart after installing Roon 2.70 Build 1665 earlyaccess

Tell us about your home network

· Not Applicable

2

Reporting what may be a “latent bug” that surfaced for me with the version 2.70 build 1665 release.

Copy/pasting Steve Beck’s comment from Feedback on EarlyAccess: Roon 2.70 Build 1665

Steve_Becker Roon Staff

Hi @Dadoo can you post this as a support issue? I think this is a latent bug and not related to any of our current changes and I don’t want to lose track of it. Would be great to know if you experience it again!

Sharing an unusual restart procedure on Mac OS with this build.

What caused me to look into the logs was that while playing music after the update, the Roon UI suddenly froze, music stopped playing, the UI became a white screen with the jellyfish in the center (due to the 2nd restart which I didn’t expect).

2026-06-11T22:17:51.692Z	06/11 17:17:48 Info: Starting Roon v2.70 (build 1665) earlyaccess on macosx
2026-06-11T22:18:13.230Z	06/11 17:18:11 Warn: ev_product_changed failed: Base.EasyHttp+HttpWebRequestEasyHttp+HttpResult

[This warning repeats 4144 more times]

2026-06-11T22:22:40.501Z	06/11 17:22:38 Debug: RoonServer, after RoonAppliance exit, exitcode: 134
2026-06-11T22:22:44.712Z	06/11 17:22:42 Info: Starting RoonServer v2.70 (build 1665) earlyaccess on macosx

The 5 minute log snippet above shows:

  • Roon restarts after installing build 1665

  • Warnings that “ev_product_changed failed” appear 4145 times

  • Roon stops with exit code 134 - anyone know what this exit code means?

  • Roon restarts

Apart from the 2 restarts, Roon seems to be operating normally.

4

Hi @Dadoo,

Thanks for your post. We should have what we need to escalate this internally, and since the issue is (ideally) not reproducing, we shouldn’t require any further logging.

We’ll post here once we have a complete idea of what you experienced. Let us know if this happens again in the meantime. Thank you!

6

Hi @Dadoo,

We’ve identified the failure and have a ticket in the pipeline to prevent this condition. We’ll share a note here as soon as the ticket is expected to merge into an Early Access release. Thank you again for the report.

9

Hi @Dadoo,

This ticket is proceeding through the pipeline and we have a fix pending. It’s not yet ready for EA, but we’ve reopened this thread since the fix will be included in one of the upcoming builds.