Normal
Hrmm... well the backdrop loading logic is all brand new with Moving Pictures 0.7, but the logic has been complete for something like 6 weeks so it has gotten a lot of testing. When I wrote this logic I also designed very carefully to free memory used by artwork that was no longer in use. You can take a look at the code yourself, but basically when a backdrop is no longer displayed, it waits five seconds, and if it is not needed again within that time frame it is unloaded. I have done quite a bit of testing of this logic to ensure that memory is freed when necessary(and just did an additional test to make sure nothing had recently broken).So based on all that I think your memory issue might be something outside of Moving Pictures. Can you identify what you are doing in MediaPortal when the memory starts rising though? Or is it just continuous when you have the application open?
Hrmm... well the backdrop loading logic is all brand new with Moving Pictures 0.7, but the logic has been complete for something like 6 weeks so it has gotten a lot of testing. When I wrote this logic I also designed very carefully to free memory used by artwork that was no longer in use. You can take a look at the code yourself, but basically when a backdrop is no longer displayed, it waits five seconds, and if it is not needed again within that time frame it is unloaded. I have done quite a bit of testing of this logic to ensure that memory is freed when necessary(and just did an additional test to make sure nothing had recently broken).
So based on all that I think your memory issue might be something outside of Moving Pictures. Can you identify what you are doing in MediaPortal when the memory starts rising though? Or is it just continuous when you have the application open?
