Rider for Unreal debugging sessions just crash out with error code 134?

This is a sanity check I guess.  Before I log this as an issue.

Every time I try and start a debug session of an unreal project, the debug session just crashes out immediately with a message about error code 134.

It seems similar (nearly identical) to this old issue: https://youtrack.jetbrains.com/issue/RIDER-47476?_ga=2.164416511.1388404853.1629582002-1133998719.1629378094

But the suggested remedies don't work for an Unreal project, because in Rider for Unreal, I don't have control over platform specifics like architecture.  The solution and project generation and files are largely out of my hands.

Am I the only one experiencing this?  Anyone got any better information?

1 comment
Comment actions Permalink

Just an update for anyone who finds this.

My error matches this newer issue:

https://youtrack.jetbrains.com/issue/RIDER-66849

A re-download and a re-install has fixed the issue.  Not sure how I ended up with debugger binaries that were not code-signed correctly.

But I'm connected and debugging.

0

Please sign in to leave a comment.