Hard lock ups after around an hour or so of tracking

[JAQK1]

Hello! Since the version update, I've been getting alot of hard lock ups after about an hour or so(nothing tracks via auto or manual tracking, can't even close the app without force closing through task manager, app completely unresponsive.) I exclusively use the Codetracker pack(latest version) with SNES9X as my emulator. For auto-tracking, I use the latest version of SNI, and the crashes occur weather or not I am streaming. Im currently on Windows 10 (OS Build 19045.6466). I've deleted and redownloaded both Emotracker v3.0.3.2 and SNI and still no luck. Any ideas what the cause may be? Thanks!

[codemann8]

@JAQK1 when you leave the tracker open, do you leave the emulator running and the autotracker connected? if so, what screen do you leave the emulator/game sit on? Do you pause the emulator?

Also, I assume with SNI you are using Snes9x-rr? what version?

[JAQK1]

@codemann8 it would always crash during runs, I have not tested if it would crash when idle or paused. Everything is running and connected when the crashes occur.

Yes sorry, Snes9x-rr ver. 1.60.

In the meantime, I have downloaded and am using Snes9x-nwa and using NWA for auto-tracking. Run 2 seeds around an 1:30 each with no crashes as of yet. I think it may have something to do with either Snes9x-rr or SNI, but I am going to keep running seeds with NWA to be sure. I'll keep you posted, thanks!

[codemann8]

I just sent out a new version of the tracker pack. Strange request, but can you install the update, reload the pack, then close Emotracker fully and reopen it fresh. Then, use it normally and let me know if it improves. Oh, and try to use Snes9x-rr with SNI like you did before. I'm sure NWA will work fine for you, but I just want to see if this improves a general stability problem with Snes9x-rr.

[JAQK1]

Gotcha, I'll run a few seeds and let you know.

[JAQK1]

Ran 3 seeds with the Snes9x-rr/SNI setup and Codetracker pack was fully up to date.

First seed went smoothly with no issues for over about an hour. (Spoiler. Build: {"Door":"1.5.6-u","Overworld":"0.7.1.3"})

Second had the hard lock up I mentioned earlier around 1 hour 20 minuet mark. (Crosskeys. Build 1.5.2-u)

Third seed had an SNI dissconnect after around an hour(SNI needed to be restarted and the LUA script reconnected, but no hard lock up). (Spoiler. Build {"Door":"1.5.6-u","Overworld":"0.7.1.3"})

All seeds were rolled with AVIANART.

No problem at all if you want a larger sample size, just let me know. Thanks!

[codemann8]

Just to confirm, are you using the Connector.lua file provided by SNI code? Because the old one from Emotracker's old directory should not be used anymore

[JAQK1]

That is correct, I use the one provided by SNI.

[codemann8]

I've been unable to replicate this. I did snes9x-rr, Lua->SNI latest and win 10 and connected everything that ik to the SNI pipeline to cause as much stress to the system. And I ran a full seed for over 3.5 hours with no problems. So I'm not sure where this problem is, but I suspect there is probably something not configured correctly, like for instance some AV or firewall program not configured to allow all connections or something. But as of now, I'm unable to replicate any issues.