Ok,
To make it crash it is necessary to do several deletes quickly,
I believe leaving things with potentially several copies of
the proginfo data for a short period of time while it releases
other copies of the data, if memory is tight enough, and enough
program info data exists, the memory deadlocks and/or gets really
slow. I have got as high as 10200 kb for the mvpmc process when
it deadlocks/gets slow, to recover the green button was required.
Right now do all of the titles/descriptions/... get loaded for
all of the recordings when one enters "watch recordings"? I would
suspect that we may need to just not load all of the data and
just load as much as is necessary for the menu.
Right now it looks like it uses around 300-500k for 400 recordings,
many more and things get ugly. Around 1k/recording.
And going into previous recordings under mythtv utilities is
instant death if you have a large number of previous recordings,
things completely lock up.
I cannot see an easy way to deal with the over memory situation,
without working out some way to reduce memory usage, removing
the reference counter would reduce some, ignoring or limiting
the program descriptions would reduce some, are their any
other things in the proginfo structure that really are not
needed?
The basic startup of mvpmc uses about 8-8.5M, I am not sure where
all of that comes from, the code and shared libraries come to
about 4M (2.7 exe, 1.2M shared libs).
Anyone know where is the rest of the 4M coming from?
Around 10M things seem to really fall apart, so there is only
about 1.5M total actually allocatable.
Roger
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/
