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

Crash after fresh install #75

Closed
rafpran opened this issue Apr 23, 2019 · 2 comments
Closed

Crash after fresh install #75

rafpran opened this issue Apr 23, 2019 · 2 comments
Labels

Comments

@rafpran
Copy link

rafpran commented Apr 23, 2019

My system: Win10, up to date
Stack:

Application: RepoZ.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
   at TinySoup.WebSoupClient+<CallWebServiceAsync>d__8.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Start[[TinySoup.WebSoupClient+<CallWebServiceAsync>d__8, RepoZ, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null]](<CallWebServiceAsync>d__8 ByRef)
   at TinySoup.WebSoupClient.CallWebServiceAsync(System.String, System.String)
   at TinySoup.WebSoupClient.PutAsync(System.String)
   at TinySoup.WebSoupClient+<CheckForUpdatesAsync>d__3.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at RepoZ.App.Win.App+<CheckForUpdatesAsync>d__13.MoveNext()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at RepoZ.App.Win.App+<<OnStartup>b__8_0>d.MoveNext()
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_1(System.Object)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Faulting module name: KERNELBASE.dll, version: 10.0.16299.1004, time stamp: 0x690aa820
Exception code: 0xe0434352
Fault offset: 0x00104622
Faulting process id: 0x1148
Faulting application start time: 0x01d4f9a420854b19
Faulting application path: c:\Program Files\RepoZ\RepoZ.exe
Faulting module path: C:\windows\System32\KERNELBASE.dll
Report Id: e04ca0f4-5be1-41ee-b5c5-e8d951bf52fa
Faulting package full name: 
Faulting package-relative application ID: ```
@awaescher awaescher added the bug label Apr 23, 2019
@awaescher
Copy link
Owner

Would you mind to help me out with this?

I suspect this code: await client.GetStreamAsync(uri) to cause the issue. However, I cannot see which file the runtime wants to load just by reading your callstack.

Would you please be so kind and check this out for me? This can be done by activating 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.

@awaescher
Copy link
Owner

Okay, I did not manage to make RepoZ crash. Since I got no further feedback, I'll close this now.

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

No branches or pull requests

2 participants