-
-
Notifications
You must be signed in to change notification settings - Fork 420
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
Release build fails for a big application #1322
Comments
Looks like a compiler bug to me. I'd make sure everything is up to date (latest compiler, latest .NET SDK). If it still doesn't work you'll have to report it on the Roslyn repo I think Another thing that I guess could be worth considering: are you using AOT or any other tree-shaking? |
I'm on Mircea's team and have been staring hard at this weird error too. :) We were wondering something like that ourselves. We have tried turning off AOT and changing the linker behavior to don't link. Unfortunately, we got the same error. Any other settings to tweak? |
To be clear, this is occurring in the Windows and Android release builds. |
Not that I know of. Differences between a debug and release build really would hint to me that it's compiler related, I'd look for the difference in builds and try working out what setting is the cause. Other than that it's anybody's guess. |
I would still expect it to fall over in the debug build though. Unless this is literally part of the release-IL optimisation. |
We have an application that it contains a lot of code. Building the app in Visual Studio in debug mode it always works fine.
When attempting to build in release mode, it takes a much longer time and in the end it throws these errors in the log (see attached files).
This happens if I build both in Visual Studio or from command line.
The reason I opened the ticket here is that I noticed that it is related to this library.
release build - partial log 1.txt
release build - partial log 2.txt
The text was updated successfully, but these errors were encountered: