[Windows] XBMC freezes when entering any directories - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228) +---- Thread: [Windows] XBMC freezes when entering any directories (/showthread.php?tid=82471) |
[Windows] XBMC freezes when entering any directories - webhead - 2010-10-04 Hello, I'm having a hard time figuring out what the issue is with this. When I enter basically ANY directory with XBMC, it immediately freezes. I have tried deleting my settings folder to no avail. I even tried a different directory without any of the meta data (nfo files and such) and it does the same thing. I notice that if it freezes, if I keep clicking around directories for a while, it's fine. Once I leave the app sitting though, it pretty much eats itself like that again. I enabled debugging and tried it: Loading my "Cartoons" directory with no meta data. Quote:15:05:49 T:3248 M:878669824 DEBUG: CWinEventsWin32::WndProcWindow gained focus Loading the parent directory (home screen for videos) a few minutes later: Quote:15:15:49 T:3248 M:880570368 DEBUG: CWinEventsWin32::WndProcWindow is active I'm really just not sure how to fix it. Having deleted the settings folder in my app data area, I'm not sure what to try next. Uninstall and reinstall? Any other tips? This makes XBMC pretty unusable at times...every directory sits there for (as you can see from the log) a good 30 seconds to a minute...which is kind of ridiculous. Edit: I uninstalled and installed the current non-beta version (9.11) and still have the same issue. I made a folder with 1 file inside of it and it still freezes. I'm really drawing blanks here...I honestly cannot imagine what is causing this. - webhead - 2010-10-07 Well for some inexplicable reason, when I leave the program open for a while it must be like...caching this stuff or something because the problem spontaneously just went away. Maybe it was doing something in the background that it wasn't telling me...I dunno. I guess I have it figured out for now. I'll post again if it comes back. |