Skip to content
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

Silent crash on latest CI build (8.0.0.6933-alpha1) start #2659

Closed
greenozon opened this issue Mar 22, 2022 · 8 comments
Closed

Silent crash on latest CI build (8.0.0.6933-alpha1) start #2659

greenozon opened this issue Mar 22, 2022 · 8 comments
Labels

Comments

@greenozon
Copy link

greenozon commented Mar 22, 2022

Steps to reproduce

  1. Download latest CI build from here https://github.com/icsharpcode/ILSpy/actions/runs/2018900654 (debug build)
  2. Run it

Error message shown

silent crash
head lines from Report.wer file:

Version=1 EventType=APPCRASH EventTime=132924536682286110 ReportType=2 Consent=1 ReportIdentifier=ac7ff5a3-aa1c-11ec-a5a5-5cf9dd47c047 IntegratorReportIdentifier=ac7ff5a2-aa1c-11ec-a5a5-5cf9dd47c047 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=ILSpy.exe Sig[1].Name=Application Version Sig[1].Value=8.0.0.6933 Sig[2].Name=Application Timestamp Sig[2].Value=6216d2c0 Sig[3].Name=Fault Module Name Sig[3].Value=KERNELBASE.dll Sig[4].Name=Fault Module Version Sig[4].Value=6.1.7601.24408 Sig[5].Name=Fault Module Timestamp Sig[5].Value=5c92f34f Sig[6].Name=Exception Code Sig[6].Value=e0434352 Sig[7].Name=Exception Offset Sig[7].Value=000000000000be0d DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.256.1 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1058 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=8ff5 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=8ff57a46ef6fc6dec66d4c16418e541a DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=da19 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=da1907f3a88e6c70410a00070a88f036 
.......

Details

PS latest release - ILSpy version 7.2.0.6844 runs OK

@greenozon greenozon added the Bug label Mar 22, 2022
@greenozon greenozon changed the title Silent crash on latest CI build run Silent crash on latest CI build (8.0.0.6933-alpha1) start Mar 22, 2022
@siegfriedpammer
Copy link
Member

ILSpy 8.0 uses .NET 6.0 and according to https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md Windows 7 is only supported, if you have access to "extended security updates", which (I guess?) you get via a support contract with MS.

@greenozon
Copy link
Author

Yeah, that might be a potential reason, but I did try to investigate more
so I've opened up .hdmp from ILSpy and inside VS I've found this:

image

the quesiton is: why the basic issue like on pic leads to silent crash?

@greenozon
Copy link
Author

Is it possible to catch these exceptions @ ILSpy level and be more user friendly to end user?

@greenozon
Copy link
Author

Issue tracked down and fixed

the bug was somehow inside the very 1st GA release of .NET6 - version 6.0.100,
after I"ve removed it ILSpy 8 alpha started up successfully! but complained I need to install .NET6,
so after installing this -
.NET 6.0 Desktop Runtime (v6.0.3) - Windows x64 Installer!
the IL8 successfully booted up @win7 x64!!!

image

BTW, why IL8 shows > 1 About tab? :)
proposing to show just 1

@yyjdelete
Copy link
Contributor

For WPF, it's an known issue
dotnet/core#7176
And seems it will never be fixed(build with newer version and run with 6.0.0/6.0.1) without the workaround in 7176
dotnet/wpf#6101 (comment)

@CreateAndInject
Copy link
Contributor

@siegfriedpammer Why not <TargetFrameworks>net48;net6</TargetFrameworks>?
I'm worried if the plugins based on .NET Framework can run.

@christophwille
Copy link
Member

No, old plugins won't run. Simply because we are also rearchitecting a few things (major version number).

@siegfriedpammer
Copy link
Member

Yes, we are moving a lot of stuff around simply to make code-sharing (or feature-sharing) a lot easier for ILSpy, ilspycmd, ILSpyAvalonia and other flavors of ILSpy. The decompiler engine will probably not see as many breaking changes, but the ILSpy APIs get a much needed makeover after many years of almost no refactorings/clean-up. In its core ILSpy is still the same as it was 11 years ago, when we quickly threw together something to get the decompiler shipped after Red Gate's famous statement concerning Reflector.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants