Posts: 28
Joined: Dec 2012
Reputation:
0
same issue here. on a build with windows 7 64bit, i5, 4gigs of ram. after closing and opening xbmc, it works fine.
Posts: 1,663
Joined: Jun 2011
Reputation:
119
I'm not 100% sure, but it seems to me that the issue begins to manifest itself when I've watched some interlaced videos and then try to watch a progressive video. Playing with interlaced method switch seems to help (except for restarting XBMC, of course), but, again, I'm not 100% sure and don't have enough statistic to confirm it, as the issue occurs rarely.
Posts: 4
Joined: Feb 2013
Reputation:
0
2014-06-25, 13:11
(This post was last modified: 2014-06-25, 13:12 by boldor.)
Same issue here, however this issue started with my setup after installing Gotham (nothing else changed).
Used Frodo without any issues, with system on 24/7.
Now I've to restart XBMC every 1-3 days...
W7x64, E8400, ATI HD6570
Posts: 2
Joined: Jul 2014
Reputation:
0
Not really a fix as such but I setup task scheduler to run RESTARTXMBC.EXE at 8am every day.
Works a treat.
Posts: 197
Joined: Oct 2010
Reputation:
0
Skram0
Senior Member
Posts: 197
I've been using v14.0 Alpha 2, and so far it's had promising results.
My system has been running for 7 days 11 hours and the video playback frame rate has stayed the same and the GUI menu scrolls left and right just as it did with a fresh reload.
Maybe this will be fixed with the release of v14!! Keep your fingers crossed. X
Posts: 71
Joined: Apr 2011
Reputation:
3
This always happens to me on a machine that I use only for XBMC and sleep between uses, I had to create a task triggered by wakeup to run a batch file to kill the process, wait a few seconds, and then start it again so it remains performant.
But, it also happens on a server machine which I double as an HTPC which never sleeps and leaves XBMC idling in a session 24/7. Generally playback seems to always be fine in that case however after a while the menus become choppy and laggy and this is on an i5-4590/HD Graphics 4600 setup which is completely ridiculous.
I could schedule a restart of XBMC at some odd time early in the morning, chances are nobody will be using it then, but it would also be annoying if somebody was by some chance using it... both of these "solutions" are too hacky to bear.
Maybe it's time to upgrade all of my machines to 14 a bit early if there are reports that this problem is finally gone for some inexplicable reason in that release.