-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.2.2, 1.2.3 Crashing on .Net Core #629
Comments
Well that's not good at all - we changed tooling to the new cc @mgravell |
Here's a fun twist: 1.2.2 and 1.2.3 cause I filed this as a comment instead of a new issue because it is also limited to 1.2.2 and 1.2.3. However, when running without a debugger attached, everything works perfectly so maybe it is a separate issue after all 🤷♂️ This certainly feels like a
Code to reproduce:redis-crash.csproj
Program.cs
When running with an external console I get this output:
In a larger project (ASP.NET Core based) where this was a problem, the crash only happens once |
Here is the crashlog:
|
@alecgorge Wow, nice findings! |
Update: this is caused by embedded debug symbols. Relevant issue: dotnet/vscode-csharp#1456 |
This appears to be fixed in dotnet/vscode-csharp#1456 now, yay! |
StackExchange.Redis 1.2.3 still seems to crash under Visual Studio for Mac 7.0.1 (build 24), it is now working properly under Visual Studio Code (on Mac). PS: 1.2.1 is working properly both under Visual Studio Code (on Mac) and Visual Studio for Mac. |
I seem to have have an issue trying to add the Stackexchange.Redis via nuget package to any projects in VS Code on ubuntu. The error I recieve is
I am trying to add version 1.2.4, but any of the old libraries seem to have the same problem. **** Update **** |
Closing this out to cleanup, fixes were external. |
I have some ASP.Net Core projects using this library,
.Net Core App 1.1 project crash without any stack trace after upgrade to > 1.2.1
.Net Standard 1.6 library project crash with following stack trace after upgrade to > 1.2.1
The text was updated successfully, but these errors were encountered: