-
Notifications
You must be signed in to change notification settings - Fork 156
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
dotnet crash on macOS #356
Comments
This is affecting Fable too 😞 |
I’ll generate a test version with don’s fix and we’ll try if I’d enough. |
Which fix? This? dotnet/fsharp#6380 |
dotnet/fsharp#6355 this is the interesting one. I'm ready to merge it into FCS and do a release as soon as it lands in master, though I suppose I could cherry pick it as it is and do a prerelease. |
Yes, i want to use a FCS with that cherry picked. |
Damn, I tried cherry-picking dotnet/fsharp@e5fcd48 into the FCS fork we're using, rebuilt and copied to assembly to Fable, but I'm still getting the SO exception :/ |
I noticed the cherry-pick hasn't updated the file timestamps and the CallFsYacc and CallFsLex targets were being skipped. This brought some hope, I run |
Anyways, I tried pushing a new |
My crashes were all related to lexing, so I'm hopeful that the fix solves my particular issue as well. I found that out by configuring my environment to take a core dump when the process crashed and loading the dump into lldb with the |
I'm getting the same as @alfonsogarciacaro, my largeish work solution still stackoverflows on FCS 28 one the netcore runtime |
there is a minimal repro with https://github.com/sjanahan/ionide-crash/tree/master thanks to @sjanahan crash in osx only the original codebase crashed also Rider (with stackoverflow backend-err.log ) but there is not yet a minimal repro for Rider
|
Using latest Ionide on macOS with latest .NET SDK I don't see a crash in the repro project. @alfonsogarciacaro @baronfel do you still see this? Could perhaps the Fable codebase be a testbed for this? CoreCLR is making improvements at the runtime level that should help but it'd be great to have something that repros today: dotnet/coreclr#25932 |
Interestingly, I just tried to build Fable with Fable in my macOS and this time worked! But I still have the dotnet SDK pinned to 2.1.403 in global.json. Not sure, why it's working now 🤔 |
Could you try it with the latest? The compiler has had many improvements around this issue, and as of the latest bits (not available in FCS I think) we think we've smashed the bulk of them. But there are still places where the compiler emits too many |
Yeah, I need to update FCS again with July's work, but the most recent version has everything through June: https://github.com/fsharp/FSharp.Compiler.Service/releases/tag/30.0.0 I've had no issues with stackoverflows for a few months now, so I'm generally happy. |
The FCS version Fable uses is based in one branch of @ncave's fork that includes a slim checker that works a bit better with Fable watch mode. I tried to udpate it but unfortunately there are a few conflicts. I'll wait a bit to see if ncave can do magic or I'll try again later :) |
Might be good to resolve this then. FWIW there will be even more fixes in a new FCS, mostly around utterly massive type definitions (e.g., hundreds of labels in a record field). |
@alfonsogarciacaro Fable FCS fork rebased to latest. |
Ok, let's close this one. It seems everything is working at the moment |
from @dustinmoris:
ref ionide/ionide-vscode-fsharp#1039
Ionide v3.33.0 => FSAC b692de8
Ionide v3.34.0 => FSAC bd342d2
The text was updated successfully, but these errors were encountered: