Enable /largeaddressaware by default ?

[Jou]

I just converted a huge ( ~ 7000, > 10 MP) batch to .jpg.
After a few thousand (usually around 1800) xnview complained "out of memory".
This is a 64 Bit machine with enough memory, there was enough avail.
So I used: editbin /LARGEADDRESSAWARE
The batch size can be much bigger now (didn't hit the limit yet).

This also solved: My fraps capture directory contains often more than 4000 pics after a long weekend with friends (all 1920x1200), but xnview crashes when opening that directory, the limit seems to be somewhere between 3500 4000 pics in one directory.
With /LARGEADDRESSAWARE: over 9000 pictures are not a problem, I did not hit the limit yet.

The ram usage in the taskmanager confirms that xnview happily uses more than 2 GB of RAM.

What do you think?

Edit: xnview 1.97.4

Edit2: For converting the limit is pushed above 3700 pics in one batch before "out of memory" appears.

[xnview]

You use 'batch convert' and you have this problem of memory??

[Jou]

The pictures are all above 10 Megapixel, ~50% above 20 Megapixel, several folders. I recompress them with higher jpeg compression (higher = 85) to save space and archive them.
The memory consumption rises quite high. Xnview eats nearly about 3 GB of RAM before that happens.
The screenshot does not show: This is a Phenoim II X4 @ 3.7 GHz, I just set the taskmanager to show only one graph.

[xnview]

Could you send a picture sample? And the script for batch convert used?

[Jou]

Several Gigabytes with a few 1000 pics? I don't think it does make sense...

I found a easy-to-reproduce way (if your don't have several thousand testpics at hand):
Get elephants dream (as source) in HD
http://orange.blender.org/download
Use virtualdub or avidemux to save it as image sequence, that should give enough source pictures. You should stop before 4000, or the xnview browser will crash without "largeadressaware" while generating the preview thumbs (my thumbs size is 430x250).

Open the folder with xnview, select all, ctrl+u, select my "overly complex" script and go.
---script---
settings( 0 1 0 0 0 0 1 )
output( jpeg 85 0 0 0 2 0 1 )
---script---

Just reproduced with the elephants-dream .jpg sequence files, same effect, including the out-of-memory message at picture number 1005.

OS is Win7 64 Bit Ult, maybe that does influence xnview's behaviour?

What about the file browser unwanted window size change bug? http://newsgroup.xnview.com/viewtopic.php?f=36&t=19116

[xnview]

Ok, i think that i found the problem. It's not batch convert.
But thumbnails build...
If you go in list mode, do you have this problem?

[Jou]

No problem with batch convert in List mode. It runs at about the double speed.
It does not eat up the memory like before. The memory usage still grows during the processing, but at a different speed (+100 MB in 10 minutes). Also the strange Kernel-time usage effect still appears (check the red CPU line in my first screenshot in this thread), but it takes longer to show up.

Still the largeaddressaware hack gives more pictures per directory in thumbs preview mode (with my huge thumbs).
I know I could not list 4000+ pics in one folder before, but now I could go beyond 10000 pictures (a bit), xnview uses 3.7 GB of RAM then.
Pictures were from elephants dream, 1920x1080.

Attached: Taskmanager during testing how many pictures xnview can take. BTW: My previous info was wrong, my thumbnail size is 480x320 with "high quality"

[xnview]

No problem with batch convert in List mode. It runs at about the double speed.
It does not eat up the memory like before. The memory usage still grows during the processing, but at a different speed (+100 MB in 10 minutes). Also the strange Kernel-time usage effect still appears (check the red CPU line in my first screenshot in this thread), but it takes longer to show up.

Before to start 'Batch convert', could you try to wait that files in the browser are checked by XnView (or press ESCAPE key)

[xnview]

I've tried again, and my free memory doesn't grow