Problem scanning huge source (mem leak)?
#91
(2017-03-06, 09:09)Rusendusen Wrote:
(2017-03-05, 18:04)DaveBlake Wrote: How about the memory leak with Library Data Provider running?

Not looking that good ;(

This is Milhouse running since yesterday evening.
LDP & skin.widget together with Xonfluence (tricked it into with adapting xbmc.gui version from required 5.12 to 5.13).
This was running over night and produced 9 crashlogs and at minimum 1 reboot Confused

Only difference seems to be that memory isn't filling up that fast as you can see from the timestamps.
Oh well, we are where we are.
For now there needs to be an advisory: don't use skins that need LDP with LE on Pi and a very large music library.

I need some more leverage to understand this. I wonder if there is any correlation between the significant drop in result dataset size (from 131k of songs to 10) and the change in memory leak? If they don't scale then it implies something else is happening too.

Since it is Pi lrelated I will have a chat with some of the team and see if they can suggest ways to investigate this further.

Thanks for the Github post too, it helps to have clear testing feedack posted.
Reply


Messages In This Thread
RE: Problem scanning source - by DaveBlake - 2017-02-12, 13:00
RE: Problem scanning source - by Uatschitchun - 2017-02-12, 21:51
RE: Problem scanning huge source (mem leak)? - by DaveBlake - 2017-03-06, 12:03
Logout Mark Read Team Forum Stats Members Help
Problem scanning huge source (mem leak)?0