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

Crashes on start (fresh install 5.0) #83

Closed
c33s opened this issue Aug 9, 2019 · 9 comments
Closed

Crashes on start (fresh install 5.0) #83

c33s opened this issue Aug 9, 2019 · 9 comments

Comments

@c33s
Copy link

c33s commented Aug 9, 2019

os: win7x64

from windows event log:

Faulting application name: RepoZ.exe, version: 5.0.0.0, time stamp: <redacted>
Faulting module name: KERNELBASE.dll, version: 6.1.<redacted>, time stamp: <redacted>
Exception code: 0xe0434352
Fault offset: 0x0000c54f
Faulting process id: 0xb0c
Faulting application start time:<redacted>
Faulting application path: C:\Program Files\RepoZ\RepoZ.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: <redacted>

is there a specific dotnet lib or c lib i have to install to make it work?

edit:
looks like my dotnet version is wrong/too old?

Application: RepoZ.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.BadImageFormatException
   at RepoZ.App.Win.App.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1_0(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at RepoZ.App.Win.App.Main()
@awaescher
Copy link
Owner

Hm, BadImageFormatException ... Would you please be so kind and check the .NET Assembly Binding Log (Fusion Log).

Luckily I just finished a user friendly tool you can use for this: Fusion++.
Just download, run and click on [Record]. Then run RepoZ and reproduce the issue. As soon as RepoZ crashes, you can click on [Stop] to check the log files and report back.

Thanks.

@c33s
Copy link
Author

c33s commented Aug 12, 2019

see awaescher/Fusion#8 (comment)

@awaescher
Copy link
Owner

I wonder if this is the same issue around System.Net.Http 4.2.0.0 - installing the .NET Framework Runtime v4.7.2 fixes this for a user over there in Fusion++.

Could you please verify?

@c33s
Copy link
Author

c33s commented Oct 3, 2019

i will give it a try

@awaescher
Copy link
Owner

Any info on this @c33s?

@awaescher
Copy link
Owner

Closing this now, please feel free to open it again.

@vncastanheira
Copy link

vncastanheira commented Nov 17, 2019

Hey, I'm having the exact same problem as the OP.
RepoZ was also installed with Chocolatey.

@awaescher
Copy link
Owner

Damn. Can you verify if the framework version v4.7.2 is installed on your machine?

As you can see in a thread about Fusion++ there seems to be a lot of confusion about the HttpClient these days.

@vncastanheira
Copy link

@awaescher Yes, it's installed on my machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants