The core does not work, constant noise and extremely slow

[ToniBC]

Hello, this core stopped working, I hear a constant noise when starting it up and it works very slow, even if you load it without game.

This did not happen before and it worked without problems. It seems that it was something of the last updates.

All tested under Retroarch Nightly and updated cores (as of this post) under Windows 10 x64.

Thank you.

[Adancete23]

Yes, same problem here.

Was working perfect some updates before, but now a strong noise in every game, and running so slow.

Thanks in advance and happy christmas!.

[DSkywalk]

Which was the release that worked correctly for you guys?

The last changes were the autorun, which doesn't affect rendering and the change for the pointer on android/wiiu, which shouldn't affect rendering either :?

I don't use windows, so I can't test it. But it's very rare that it happens to two users at the same time. Could you upload your retroarch configuration? Could you post the RA startup log with verbose arg?

Thanks and happy holidays!

[ToniBC]

Apparently the error is related to the latest versions of Retroarch, I would have to look to see from what version happened, but with the latest nightly that core does not work. I think it only affects Caprice's core. With the 1.9.14 stable it does work, but it would be a problem with the 1.9.15 release.

[DSkywalk]

ping @twinaphex ! :sos:

[ToniBC]

The oldest version of Retroarch.exe is the one from the 20th, that one continues to fail, if you put the .exe of that Version or later, the core stops working.

The latest versions would have to be reviewed, it could be a problem with the new options format or something like that or with the netplay.

I enclose the logs, of the last nightly and the stable.

retroarch (1.9.14 stable).log retroarch (last nightly).log

Thank you.

[veganvelociraptor]

Same error occurs with a freshly cloned and compiled git snapshot of Retroarch.

I've no idea what has changed or why it only affects this core.

Update: I just discovered the Atari Virtual Jaguar core has the same issue.

[ToniBC]

Interesting and curious that it also happens with the Jaguar. Let's see if they find out what it is, because with the release of the new version that will soon be released, many more will say so.

[veganvelociraptor]

I've checked the different commits for Retroarch, since this issue started after the Christmas holidays.

Just like someone else suggested, the majority of changes are in the netplay code. And I don't see how this should affect cores when not using netplay. Nevertheless, it must be a new bug of some kind in Retroarch. I'll see if I can spare time to dissect the commits, and I'll report the bug to the Retroarch repo if I find the cause.

Update: Didn't take me long to find the cause. Commit e3217b4 described here has the issue. Whereas the previous commit e954a46 doesn't.

The issue with Virtual Jaguar seems unrelated though. Haven't tested all cores, but so far only Caprice is affected.

[DSkywalk]

really thanks for your dissect, i'll try to reproduce on linux :+1: