You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the latest gambatte core and the latest Retroarch code on Mac OS (High Sierra), enabling Runahead makes the application / core freeze after around a minute of gameplay. You need to use a force-quit shortcut (Option+CMD+Esc) to quit the application.
This happens all the time, regardless of whether Second Instance is activated and irrespective of the specific content loaded (GB game, GBC game, etc.). The same core works perfectly with Runahead on Windows.
It just occurred to me that this issue is most likely related to the fact that save states were broken (see PR #117) - i.e. after some length of time with run-ahead enabled, an uninitialized variable was randomly assigned a 'bad' value that trapped the core in an infinite loop. Save states are fixed now - could you try again?
With the latest gambatte core and the latest Retroarch code on Mac OS (High Sierra), enabling Runahead makes the application / core freeze after around a minute of gameplay. You need to use a force-quit shortcut (Option+CMD+Esc) to quit the application.
This happens all the time, regardless of whether Second Instance is activated and irrespective of the specific content loaded (GB game, GBC game, etc.). The same core works perfectly with Runahead on Windows.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: