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

[Mac OS only] Enabling Runahead makes the application / core freeze after a minute #107

Open
Ryunam opened this issue Aug 6, 2018 · 2 comments

Comments

@Ryunam
Copy link
Contributor

Ryunam commented Aug 6, 2018

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.

@inactive123
Copy link
Contributor

@Dwedit Might have something to do with the fact that the macOS port uses a different runloop as opposed to Windows/linux -

https://github.com/libretro/RetroArch/blob/master/ui/drivers/ui_cocoa.m

@jdgleaver
Copy link
Contributor

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?

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

No branches or pull requests

3 participants