2015-04-06, 22:17
Hi all,
This has been occurring every 2 or 3 days since I first migrated from Gotham to Kodi. I've updated the .exe several times, which has fixed some other issues, but this kind of crashing is still a semi-regular occurrence.
The usual sequence of events is this. Turning on my TV or switching to Kodi after a long absence, I can navigate around the interface the same as usual, but I cannot exit or minimize or put it in a window. There is no sound (the navigational "pips" and clicks that I would normally expect). If I select a file to play the content will start, but with no sound, and then freeze. And at that point my only option is to bring up task manager and kill the process. I must leave the process killed for about a minute or else I will not be able to launch Kodi at all; just killing and immediately relaunching will do nothing at all.
I cannot reproduce or isolate the conditions that are leading up to the failure, but this happen at worst once a day, at best every 2 or 3 days. For this reason, I cannot keep the keyboard and mouse locked up, as I planned. Once in this condition there's nothing I can do with the remote that will work.
Any ideas? The PC is an i3 with 16GB of RAM running Windows 7/64 Professional.
This has been occurring every 2 or 3 days since I first migrated from Gotham to Kodi. I've updated the .exe several times, which has fixed some other issues, but this kind of crashing is still a semi-regular occurrence.
The usual sequence of events is this. Turning on my TV or switching to Kodi after a long absence, I can navigate around the interface the same as usual, but I cannot exit or minimize or put it in a window. There is no sound (the navigational "pips" and clicks that I would normally expect). If I select a file to play the content will start, but with no sound, and then freeze. And at that point my only option is to bring up task manager and kill the process. I must leave the process killed for about a minute or else I will not be able to launch Kodi at all; just killing and immediately relaunching will do nothing at all.
I cannot reproduce or isolate the conditions that are leading up to the failure, but this happen at worst once a day, at best every 2 or 3 days. For this reason, I cannot keep the keyboard and mouse locked up, as I planned. Once in this condition there's nothing I can do with the remote that will work.
Any ideas? The PC is an i3 with 16GB of RAM running Windows 7/64 Professional.