Images in lists using a lot of memory

[cncb]

If I display images in an icon list an unexpected large amount of memory is being consumed.

For example, I created a test plugin which shows the same image in 100 items, each one loaded by a separate System.Drawing.Image.FromFile(). The image is a jpeg only 224 KB big, but NPVR consumes over 500 MB of memory displaying them in a list. Any ideas what is causing this? Does scaling the image for display consume a lot of memory?

I can, of course, use IGetImageCallback but reloading the images each time causes delayed scrolling/paging.

[mvallevand]

I had to lots of hacks to get around this in MB3 and MB4. My backend is only 2GB and whatever is going on eats a huge amount of memory. I know disposing my images does help http://forums.nextpvr.com/showthread.php...n-disposed even though sub wrote it shouldn't may be it is just garbage collection, I found disposing each element in the uilist manually helped my memory use a lot too.

I do create and I enforced a limiit of 100 image, to avoid going over 1.5GB.

Martin

[sub]

For example, I created a test plugin which shows the same image in 100 items, each one loaded by a separate System.Drawing.Image.FromFile(). The image is a jpeg only 224 KB big, but NPVR consumes over 500 MB of memory displaying them in a list. Any ideas what is causing this? Does scaling the image for display consume a lot of memory?

If you want to supply your test plugin, I can take a look where the memory is being used. The built-in NextPVR screens using this list with a 100 items aren't typically using that much memory. For example, trying the Video Library with a directory with a 100 subdirectories, viewing in icon mode, doesn't use a lot of memory. Even if these are just showing text, NextPVR is still allocating it's images and renderering them.

If you load these 100 x 224KB images, but don't put them in to the list control, how much memory is your process using? How much does it increase to when you insert them into your list control?

The memory used by the list should be whatever you've put in the list, plus 50 rendered list objects in a cache. These rendered objects are effectively a RGB bitmap of the same size as the pixels that'll appear on the screen (when you're fullscreen). If you're your system doesn't have dedicated video memory, then the process may also contain texture memory allocated by Direct3D or your video card. You can try running "NextPVR.exe -no3d" to run the process, which disables Direct3D

If you minimize the process, then bring it back to the foreground, does it make any difference? This will often cause .NET garbage collection.

[cncb]

Sorry, apparently it doesn't have anything to do with NextPVR. It seems that System.Drawing.Bitmap's are just very big for some reason. If I just load up the 100 images and don't add them to the list, it pretty much uses the same amount of memory.

[sub]

Yeah, I suspected that'd be the case. Phew for me