You are not logged in.
Pages: 1
I discovered that after the latest xbmc updates I run into memory problems with my xbmc installation. Without starting xbmc my system uses about 500MB of Ram. After starting xbmc it takes about 5 minutes until all my memory ~8 GB is used. Has anybody else similar problems?
Offline
I never had issues with xbmc.
Are you using the official version of xbmc or the nightly build on AUR?
I divide by zero, multiple times per day. Also, I don't believe in tipping
Arch + i3wm (still learning)
Offline
I'm having the same problem.. Since the last upgrade XBMC has a massive memory leak.
What's weird is that the allocated memory isn't shown by top/ps etc, and is not detected by valgrind.. So far I have no luck finding the source of the leak
The best solution to a problem is usually the easiest one.
Offline
Same problem here. Also I cannot completely kill xbmc, the xbmc.bin process (a child of xbmc) will stay "alive" as a zombie process.
Offline
Do you use the Catalyst driver (13.8b)? Because I think I read this is the source of the memory leak.
Offline
Yes, I do. Is there anything I could do to get it working again (exept downgrading)?
Offline
Yes, I do. Is there anything I could do to get it working again (exept downgrading)?
Only downgrading, afaik.
Offline
I've always disliked xbmc's bloat, and this memory leak finally convinced me to ditch it. I'm now writing some scripts to make my own simplistic mplayer-based solution ![]()
The best solution to a problem is usually the easiest one.
Offline
It's most likely not xbmcs fault, but the 13.8 radeon drivers: http://ati.cchtml.com/show_bug.cgi?id=866
Offline
I've always disliked xbmc's bloat, and this memory leak finally convinced me to ditch it. I'm now writing some scripts to make my own simplistic mplayer-based solution
How is XBMC bloat, if it runs on the Raspberry Pi?
Offline
Pages: 1