Windows Client closes frequently

[jellis413 4]

See my post here, figured I would start my own topic in case they are different issues:  

Here was my original post in that thread:
I figured I would add-on to this thread, but if it should be separated out into its own, that is fine as well. Since the latest Windows client update, sometimes it immediately exits out/closes and I have to go back into it. This usually only happens once, rarely twice (but when I turned on debug logging, it happened three times in a row).  Then when I go to play something, about 50% of the time it will exit/close out and I have to go back in and then it will usually play fine (sometimes it will close twice).  

If it helps, I use the WIndows Client with Zero Tier as my virtual network (same concept as Tailscale if you are not familiar) and this is the only Windows Client I have.  This does not happen with any of my other Android clients (local network to the server or over ZeroTier network).  I will PM the log files you listed above.  

I should also note that everything was fine (and nothing has changed) before the Windows client was updated.  Let me know if you need anything else from me. Thank you.

 

I sent the debug log files via PM to softworkz yesterday based on the info requested from Crusher11

 

 

[softworkz 5264]

Thanks for sending the logs. Yet it seems you have sent the log from the session which you started to get the log rather than from the session which exited before. (the logs from from earlier sessions have a timestamp in the name)

Can you see anything in the Windows event log about app crash or something?

[jellis413 4]

Yes, I see a .NET error and then immediately (every time there is a .NET/app crash) a coreclr.dll error.  Maybe re-install .NET is my solution?  Anyway, here is one of the Event Viewer for both:

the errors from one of the events for both .NET and CORECLR.DLL are attached.  Thank you for your assistance.

 

Net.txt coreclr.txt

[softworkz 5264]

@jellis413

Thanks a lot for the details. That exact error has been fixed just two days ago. A new stable release will be out by the end of the weekend. Thanks again for reporting!

[jellis413 4]

Thank you!