socketInitializeDefault sometimes never returns
friedkeenan opened this issue · comments
This issue only occurs on master, not the latest release.
Here is an example to show the issue. It calls socketInitializeDefault
, and then when you repeatedly press plus, which does envSetNextLoad
on itself and then exits, eventually socketInitializeDefault
will never return, and the console will require a reboot to get out of it.
Does that happen with normal hbmenu-return + app launch?
Well, this is strange. Doing it that way I eventually get a hang that requires a reboot, but it doesn't print Before socketInitializeDefault
See commit above. Thank you very much for making us catch this glaring bug :)
Thank you for fixing it :)