Stride Game Studio crash on nugget dependencies change
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Release Type: Official Release
Version: 4.2.0.2381
Platform(s): Windows
Describe the bug
Just had the Stride Game Studio crash.
I was experimenting with some .NET libraries, and installed Microsoft.CodeAnalysis.Common 4.13.0 through Rider Nuggets manager.
On the next time opening the project both Rider and SGS showed me the error related to this (see the logs section).
Pressing Play in SGS was only repeating the error.
Since I have had already removed the libraries that required Microsoft.CodeAnalysis.Common 4.13.0 , I just removed this dependency in Rider nuggets manager as well.
Upon switching back to SGS it said it crashed and showed the crash report form.
I was unable to fill the crash report form becase after I wrote the first line of the message and pressed enter, all SGS windows, including the crash report form, closed.
I have no idea if it considered me pressing enter to mean sending the message, or if it just finally totally crashed, idk. But one thing for sure: pressing enter in the text editor should not send the form.
To Reproduce
I will just describe what I did, but maybe it doesn't have to be this specific.
Steps to reproduce the behavior:
- Create and open the CSharpIntermediate sample project of Stride
- Install the Infer.NET package
- It requires the
Microsoft.CodeAnalysis.Common 4.13.0dependency, so I install it - Uninstall Infer.NET, the dependency remains.
- Restart both Rider and SGS, see the error
- Press Play in SGS once, see the error
- Uninstall the nugget package of
Microsoft.CodeAnalysis.Common 4.13.0 - Go back to SGS and see the crash.
"Install" and "uninstall" means using the Rider nugget manager to add or remove the package.
Expected behavior
No crash
Log and callstacks
Added the logs. I also added some newlines into it for easier reading, since the original compiler message doesn't want to make it easy.
package-version-conflict.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the package sequence in the CSharpIntermediate sample: install Infer.NET, restart Stride Game Studio, then remove Microsoft.CodeAnalysis.Common 4.13.0. Start by reading package-version-conflict.txt and compare the errors before and after removal; done means the project opens and runs without the dependency change crashing Stride Game Studio.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100