Weird emulator issue

[Aroth Khasar]

So I have a strange issue that only seems to pop up with emulators, and even then only with s9xTYLmecm and gpSP (both Kai and J). Basically if I set the PSP down for more than 90 seconds or so (roughly the time it would take for the screen to timeout and dim), the emulator freezes, then about 5 to 10 seconds later the system shuts off with a speaker pop.

I was thinking at first that it may have been related to a conflict between the system trying to sleep and the emulator being unable to, but seeing as it only happens with those two (and their variants) I am not so sure anymore.

Anyone have any ideas what could be going on?

[BlueIon]

Nope

[Aroth Khasar]

Well crap. Anyone else have any ideas or input?

[greg]

what firmware you running?

[Aroth Khasar]

I am running 6.60 ME v1.4 and am using the most recent version of both s9xTYLmecm and gpSP Kai that are posted in the emulator/homebrew list on the forums here. Using Kai instead of gpSP-j because -j doesn't support cheats, but I had the same experience with the most recent version of gpSP-j I could find as well.

Huh, apparently I am having the issue with PSP games as well now... wtf?

Update: I switched to the PRO firmware earlier today to see if it would fix another issue I have been having and am still experiencing this issue on it as well.

Update (again): Ok so as part of an attempt to solve another (possibly related, not sure yet) issue, I reverted back to the 6.39 ME-8 that I was using prior to updating to 6.60, and the issue is completely gone. Apparently there is an issue inherent to 6.60 and present in both the ME and PRO firmwares that causes any running program (game or homebrew, possibly even video or other media) to crash if it the user doesn't provide some form of input for more than 45 seconds or so. This could possibly be related to the screen timeout and/or automatic sleep functions of the system itself. This same error, or a related one) also apparently prevents anything other than the XMB to be outputted to a secondary display, causing the system to crash in the same manner as the previous bug.