Memory leak (closing image editor)

[nji9]

I cannot tell where/ when exactly mem leak happens...
but it happens doing this:

Start XnViewMP
Category Filter: choose to de-select (Alt-Leftmouse) some category.
Have a look at the result pane.
Open an image here and there.
From time to time check/ decheck some category of some image
in category filter sets pane.
That's OK for some time (Some dozens images).
Then mem consumption slowly starts rising whenever an image is opened.
A screenshot short after closing MP:

Clipboard_02-15-2026_01.jpg

Recently I had the effect that MP didn't react anymore at some point
- I had to kill it. The mem consumption was at max then.
Maybe it was exactly that cause?

XnViewMP 1.9.10 @ Win7-64

[xnview]

if you don't open image in edit mode, same problem?

[nji9]

If I do not open image in edit mode (but still assign/ unassign categories in category set pane): No mem leak.

If I do open (and afterwards close) image by image in image mode (and don't do any category assign): Mem leak.

[nji9]

Even simpler:

To get the effect you don't need to have a Category filter active.

==> Mem leak is from opening images in edit mode (mem not released when closed again?).

[nji9]

Additional info:

I checked on 14MP JPG images; i.e. mem for each: 41.45 MB.

Whenever I open an image to the image editor, XnViewMP uses abt. 47 MB more mem.
When I close the image without having done anything ... (guess! )... the mem isn't given back.

[xnview]

from browser i've tried to open a large JPEG but memory stays the same. Please send us the sample file?

[nji9]

Sorry, I do not understand what you mean.

From browser you opened a large JPEG to image editor, right?
==> memory usage of MP should increase by its uncompressed size.
Does it for you?
(If not I would like to buy your computer )

Now closing the image editor again.
==> memory usage of MP should decrease to about the former size.
Does it for you?

What kind of "sample file" are you asking for?
It won't be some image...
... as that won't make any sense (The effect is for arbitrary images).

[xnview]

From browser you opened a large JPEG to image editor, right?
==> memory usage of MP should increase by its uncompressed size.
Does it for you?
(If not I would like to buy your computer )

Now closing the image editor again.
==> memory usage of MP should decrease to about the former size.
Does it for you?

yes normal, you have not that?

[nji9]

From browser you opened a large JPEG to image editor, right?
==> memory usage of MP should increase by its uncompressed size.
Does it for you?
(If not I would like to buy your computer )

Now closing the image editor again.
==> memory usage of MP should decrease to about the former size.
Does it for you?

yes normal, you have not that?

Maybe you occassionally haven't read my post above:

Additional info:

I checked on 14MP JPG images; i.e. mem for each: 41.45 MB.

Whenever I open an image to the image editor, XnViewMP uses abt. 47 MB more mem.
When I close the image without having done anything ... (guess! )... the mem isn't given back.

Actually that's the wit about the bug...

[xnview]

Actually that's the wit about the bug...

i can't reproduce. Send us a sample file used and how to reproduce...

[nji9]

i can't reproduce. Send us a sample file used and how to reproduce...

From MP browser double-click an image (raw mem: 48MB) to open the image editor.
Mem usage of MP increases by about that 48MB.
Now (without having done anything in editor) close image editor.
Would expect MP's mem usage to drop 48MB again.
But does not!
Opening the same file again: No additional mem usage.
Open a different file: Additional mem usage.
(Again and again for every different image, until MP's freeze).

It happens for every image.
But as you asked for it, here some arbitrary images..

[xnview]

can't reproduce. Do you use settings>Misc>Cache? and in Settings>View>Zoom out/in?

[nji9]

Do you mean? Settings>View>Misc>Cache?
I can't remember ever having touched this.
However "Keep.." and "Read.." both were activated.

If I de-activate "Keep..."... the effect of cummulative mem usage when closing image editor remains.
(But even with "Keep..." activated, MP shouldn't accumlate mem until freeze I might think).

If I additional deactivate "Read.."... the effect stays the same.

I do not know what you mean by Settings>View>Zoom out/in.
Do you mean Settings>View>Anti-aliasing: Zoom out/ Zoom in?
As before I can't remember having ever touched that.
However my settings are "Bilinear" and "none".
If I change "Bilinear" to "none"... the mem effect does not change.

If I use MP only for single image view (i.e. no browser etc.) mem usage does not accummulate.

BTW:
As you can't reproduce: As mentioned in my first post, it's @ Win7-64.
You will have tested?
However other apps at Win7-64 do not accummulate mem usage:
GIMP, PSP, IrfanView.
Conclusion: The bug is of XnViewMP.

[xnview]

tried on Win7 with default settings, and all is ok, open and close image file in edit mode, stay around 72Mb and 22Mb if deselect it in browser...

[nji9]

tried on Win7 with default settings, and all is ok, open and close image file in edit mode, stay around 72Mb and 22Mb if deselect it in browser...

Deselect it in the browser?
Selection status in browser doesn't has any effect on mem usage (at least with me).