Serious Memory Leak With Frodo
#1
So literally everyday sometimes multiple times per day I run into an issue where XBMC will take up to 3.5gb of my RAM and will cause my system to completely stop responding. When the memory usage is a little lower it will generally stop showing thumbnails and won't allow me to do anything but scroll through the main menu. Essentially this results in my having to hard reboot my system many times per day. Has anyone else experienced this or can anyone shed some light on it? In going through the debug log I am thinking it may have to do with the Library Watchdog addon but I am not 100% on this. I have disabled it as a test to see if the issue continues to appear.

Debug Log
Reply
#2
Your observation is likely correct. Smile
Reply
#3
Ouch, I hope I never run into that. I only have 2GB of RAM. XBMC, at start, seems to only use about 1GB of RAM.
But maybe that's the side affect of some of the issues I've been having too, don't know.
Reply
#4
Watch dog doubled my cpu usage, thats why I dont use it.
Reply
#5
I have a core i7 and 12gb of ram so I wouldn't care if it consumed more resources if it would work correctly. Since I disabled library watchdog a couple days ago I have not had a single memory issue. I am going to continue this test and then I will try re-enabling it to watch for the issue again.
Reply
#6
Care to post a debug log with that (debug, not info log)? If it is the addon then disabling it midways should free all the memory it consumes. Btw, the amount of memory the addon actually consumes should at least be far less than 100mb. If it's beyond that than there's something wrong.
Reply
#7
Sorry the log I posted in the initial post was not a debug log? I have debug enabled because I have been troubleshooting this issue. Also it is not possible for me to do anything with my computer when this happens so I would not be able to test out your theory of disabling the add on. Literally I can only do a hard reboot. Nothing on my system will respond.
Reply
#8
(2013-02-25, 18:54)mobias1313 Wrote: Sorry the log I posted in the initial post was not a debug log? I have debug enabled because I have been troubleshooting this issue. Also it is not possible for me to do anything with my computer when this happens so I would not be able to test out your theory of disabling the add on. Literally I can only do a hard reboot. Nothing on my system will respond.
"09:38:24 T:2068 NOTICE: Disabled debug logging due to GUI setting. Level 0."
The crash is because the system runs out of memory, so simply watch the memory usage and stop it when it reaches 1gb (or whatever is abnormal. I don't know what xbmc normally use on windows)
Reply
#9
Hmm that's strange. I will have to look into why that's turned off. As for watching the memory usage, I would be happy to do so but it doesn't always happen when I am watching the system and usually if it does I am unable to do anything. I will first notice it because all of my thumbnails will stop working and then the entire system locks up if I select anything. I will try however.

I apologize for the debug setting issue. I must have overwrote it in my advanced settings.XMl when I was testing out refresh rate changes. My bad.
Reply
#10
I can confirm this, but under Linux.
XBMC on ubuntu started yesterday before midnight.
Then it was sitting there and scanning the library, all ok.
But suddenly at 7 AM it went avot and decided to eat all ram:

Image


It had eaten 16GB or ram and kept going, the rest of the system went to swap, eventually 16GB RAM and 16GB of swap were just wasted by the app.
Tried to kill it it took a LOT of time to recover, but system was stable.
Not sure if it quit by itself when pressed exit, or if the kill or kill -9 worked.

I know that I have watchdog enabled, but there was not new files uploaded to the watched media libraries.

The only thing I can think of is XBMC auto backup that starts every day at 7AM.
Reply
#11
Im able to reproduce the leak with XBMC in combination with the watchdog addon. But, it's no where near the order of magnitude other people a reporting. After ~16 hours on I went from 100MB to a bit over 400MB. However it's not Watchdog that's leaking, and here's an instance count to show it:

At time 0:
Code:
17:56:50 T:139772947515136  NOTICE: leaking_objects: 531  [note to reader: includes gc roots]
17:56:50 T:139772947515136  NOTICE: function                   4208
17:56:50 T:139772947515136  NOTICE: dict                       1543
17:56:50 T:139772947515136  NOTICE: builtin_function_or_method 1270
17:56:50 T:139772947515136  NOTICE: wrapper_descriptor         1157
17:56:50 T:139772947515136  NOTICE: weakref                    997
17:56:50 T:139772947515136  NOTICE: tuple                      960
17:56:50 T:139772947515136  NOTICE: method_descriptor          809
17:56:50 T:139772947515136  NOTICE: list                       749
17:56:50 T:139772947515136  NOTICE: set                        474
17:56:50 T:139772947515136  NOTICE: getset_descriptor          453
17:56:50 T:139772947515136  NOTICE: module                     314
17:56:50 T:139772947515136  NOTICE: member_descriptor          280
17:56:50 T:139772947515136  NOTICE: type                       268
17:56:50 T:139772947515136  NOTICE: WeakSet                    192
17:56:50 T:139772947515136  NOTICE: property                   180
17:56:50 T:139772947515136  NOTICE: frame                      144
17:56:50 T:139772947515136  NOTICE: instancemethod             129
17:56:50 T:139772947515136  NOTICE: classobj                   120
17:56:50 T:139772947515136  NOTICE: _Condition                 113
17:56:50 T:139772947515136  NOTICE: classmethod                71


After ~16 hours on-time:
Code:
17:25:03 T:139772947515136  NOTICE: leaking_objects: 533
17:25:03 T:139772947515136  NOTICE: function                   4208
17:25:03 T:139772947515136  NOTICE: dict                       1545
17:25:03 T:139772947515136  NOTICE: builtin_function_or_method 1270
17:25:03 T:139772947515136  NOTICE: wrapper_descriptor         1163
17:25:03 T:139772947515136  NOTICE: weakref                    997
17:25:03 T:139772947515136  NOTICE: tuple                      959
17:25:03 T:139772947515136  NOTICE: method_descriptor          811
17:25:03 T:139772947515136  NOTICE: list                       749
17:25:03 T:139772947515136  NOTICE: set                        474
17:25:03 T:139772947515136  NOTICE: getset_descriptor          453
17:25:03 T:139772947515136  NOTICE: module                     314
17:25:03 T:139772947515136  NOTICE: member_descriptor          280
17:25:03 T:139772947515136  NOTICE: type                       268
17:25:03 T:139772947515136  NOTICE: WeakSet                    192
17:25:03 T:139772947515136  NOTICE: property                   180
17:25:03 T:139772947515136  NOTICE: frame                      144
17:25:03 T:139772947515136  NOTICE: instancemethod             129
17:25:03 T:139772947515136  NOTICE: classobj                   120
17:25:03 T:139772947515136  NOTICE: _Condition                 113
17:25:03 T:139772947515136  NOTICE: classmethod                71

Looks to me like XBMC is leaking and the addon merely triggers it. The addon calls the methods in xbmcvfs, a lot. Enough that leaking a few bytes for every call adding up to gigabytes seems plausible. I guess that's one place to start..
Reply
#12
BUMP

Been having the same issue since upgrading to F12RC2.

My wife is very angry with me about this...
Reply
#13
I'd like to add myself to this issue.

Windows 8 XBMC 12.1.

Since 12.1 it will randomly crash out, and windows advises that it closed the app because it was out of RAM.
I have 4Gb and no page file, and xbmc is the only thing that is really running. After it crashes, I have 12% memory used.

Most times it will have hung the whole system and I need to remotely restart the OS, other times it has crashed out (as above).
When i'm watching it, it seems fine... it only happens when we go away for some time and come back to it.

lol! I started disabling some addons and when I got to the watchdog, I hit disable and xbmc crashed to the desktop.
MS Visual C++ runtime library - runtime error.
Reply
#14
try 12.2pre
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply
#15
(2013-02-23, 06:11)mobias1313 Wrote: So literally everyday sometimes multiple times per day I run into an issue where XBMC will take up to 3.5gb of my RAM and will cause my system to completely stop responding. When the memory usage is a little lower it will generally stop showing thumbnails and won't allow me to do anything but scroll through the main menu. Essentially this results in my having to hard reboot my system many times per day. Has anyone else experienced this or can anyone shed some light on it? In going through the debug log I am thinking it may have to do with the Library Watchdog addon but I am not 100% on this. I have disabled it as a test to see if the issue continues to appear.

Debug Log

Hi!

What security software do you have installed? and where is XBMC installed, and is UAC enabled in the OS?
The Problem is not the problem. The problem is your attitude about the problem.
Do you understand?
Reply

Logout Mark Read Team Forum Stats Members Help
Serious Memory Leak With Frodo0