.NET

1484 readers

7 users here now

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

Rules

Rule 1: Follow Lemmy rules
Rule 2: Be excellent to each other, no hostility towards users for any reason
Rule 3: No spam of tools/companies/advertisements

Related communities

Wikipedia pages

.NET (open source & cross platform)
.NET Framework (proprietary & Windows-only)

founded 1 year ago

MODERATORS

erlingur

starman

Spyros

Help Request: Rider IDE Crash on Ubuntu 20.04 (self.dotnet)

submitted 1 year ago by xcjs to c/dotnet

5 comments fedilink hide all child comments

I've had an issue while using Rider IDE on Ubuntu 20.04.

Every time I debug a project and then stop debugging, Rider crashes immediately without an error message.

I did find that if I start Rider from a terminal or using the Jetbrains Toolbox that it does not crash afterward when I stop debugging. I'm not sure, but I'm assuming this is because Rider has a parent process in that case.

Has anyone run into this issue? It's been driving me crazy since I usually launch Rider via the application menu or similar means.

top 5 comments

sorted by: hot top controversial new old

[–] miniu 2 points 1 year ago (2 children)

Jetbrains are pretty responsive on their issue trackers. Maybe try reporting/asking there. I've had good experiance with them so far. https://youtrack.jetbrains.com/issues

[–] xcjs 1 points 1 year ago

I think I'm going to take your advice on this. It's driving me insane and my attempted solution did not work.

[–] xcjs 1 points 1 year ago

Reported here: https://youtrack.jetbrains.com/issue/RIDER-102338/Rider-Crashes-When-Clicking-Stop-Project-After-Debugging-in-Ubuntu-20.04

Thanks for the link and advice!

[–] xcjs 1 points 1 year ago* (last edited 1 year ago) (1 children)

Alright, so I think I may have solved it. I reset Rider to its default settings, and it worked at least once. I'll try again later to confirm that was the fix.

[–] xcjs 1 points 1 year ago* (last edited 11 months ago)

Nope - I'm still having the issue. I'm going to follow the advice I received here to file an issue.