The most common causes of this issue are: It should be fixed now with the aforementioned PR as you've experienced it yourself.Your IP address has been temporarily blocked due to a large number of HTTP requests. Can be disabled by locking the core, but should be avoided for obvious reasons, unless you've some very specific reason(s) not to want a sync to the latest core version.Īchievements were deadlocking when reloading content for netplay, then it got fixed, then the fix got reverted because it broke something else. The short "freeze" is the netplay auto core updater updating your core in the background to ensure you always netplay at the latest version. Whereas the one I posted about above was c97bc0d and that would freeze every time (like I waited until my phone said that the app wasn't responded and asked me if I wanted to wait or to close it). This latest one appeared to freeze for a bit when starting netplay but then ultimately connected. This latest one that I just downloaded is 85c44f9. So I updated to the latest nightlie again and I assumed it was going to be the same one that I posted above (since the build date was still the 23rd) but it was a different Git Version. I'm going to stop confusing myself by testing all different version of RetroArch and wait for you to reply back to see what exactly you may need me to do next. Whereas the one I posted about above was c97bc0d and that would freeze every time (like I waited until my phone said that the app wasn't responded and asked me if I wanted to wait or to close it).Īnyway, what I am getting at is that I thought it was weird that latest stable I had the freeze, updated to latest nightly at the time and netplay worked but crcs were messed up, updated again to latest nightly the next day and crcs were correct but netplay froze again, then just now updated again to latest nightlie and everything seems to work now.īottom line is it appears with this latest nightlie (Git Version 85c44f9) both the crc issue and the netplay freezing issue are fixed. Other then that, please let me know what else you'd like for me to try out and I'd be more than happy to do it. I'll get you that stacktrace as soon as I know how to create one and make it crash again. So that's all I've done and noticed so far. Let me know if this is unrelated and you'd like for me to create a new issue. I'm attaching screenshots so you can see what I mean. But on the nightlie, there are a bunch of "F"s in front of it. Using the stable and refreshing netplay hosts, the crc of the rom looks normal. I noticed another possible issue when comparing netplay with the current stable to the nightlie. I did have it crash on me again randomly so I'd like to see if I can make it happen again and get you that stacktrace. How do I provide you with a stack trace of the crash? I see the Logging options under settings but not sure which options need to be enabled. "The crash you are experiencing may or may not be related to netplay hard to say since you can't reproduce it other than that one time and you didn't provide/have a stacktrace of the crash." You had said over there (and please forgive me, I don't know how to quote from another issue): I am continuing our discussion over here as requested. Thank you for your reply in the other issue report.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |