100% CPU and frozen picture

Help and Support Vero
21

Thanks!!

That run properly.-

http://paste.osmc.io/ojomuqedec

regards

22

You seem to have “component-specific logging” for SMB enabled - this will be causing massive debug logs and may actually be causing you issues, so go back into Settings->Debugging and make sure you turn off “Enable component-specific logging” but leave “Enable debug logging” turned on.

Then reboot twice to clear out the old huge Kodi logs, try to reproduce the problem where you run out of memory again then use:

grab-logs -A

The logs should be small enough to upload then. Unfortunately fzinken’s suggested logging options don’t provide the system journal, which is actually the most important thing for out of memory conditions. (But all logs is best of course because you never know what you’ll need until you see it sometimes)

23

Now I don´t have access to the raspberry, I only can access using ssh, so I can modificate the file advancedsettings.xml and reboot.

Looking the documentation: [Kodi_doc_page_advancedsettings][1]

I can try:
<advancedsettings> <loglevel>2</loglevel> <!-- Change this to "1" to hide the on-screen debug log text --> <debug> <extralogging>true</extralogging> <setextraloglevel>64,128,256,512,1024,2048,4096,8192,16384,32768,65536</setextraloglevel> <showloginfo>true</showloginfo> </debug> </advancedsettings>
removing the 32 respect the las log, it is a good idea?

Thanks!!
[1]: http://kodi.wiki/view/Log_file/Advanced

24

I would set extralogging to false. That should be component specific logging.

25

2 posts were split to a new topic: 100% cpu and frozen picture on Pi