XnView Software

jadO wrote:

xnview wrote:it's only for create catalog in settings

I don't understand what you are trying to say.

I had been wondering if the fixed leaks were also causing the OOM issues reported by you, jadO.
Thanks for clarifying, Pierre.

jadO wrote:I don't understand what you are trying to say.

The problem fixed is when you 'add folder' in catalog setting

This seems to be still an issue. It seems that memory consumption is growing more slowly now, but still it keeps growing and growing and growing.

Edit: It is now using appr. 1GB. But stays at that for some time now. Has that issue been fixed?

Edit 2: It remained at about 1GB for a while but started to grow again after some time causing XnviewMP to crash.

Still memory leaking.

jadO wrote:Still memory leaking.

how do you have this memory leak? do you use internal codec or ffmpeg?

xnview wrote:

jadO wrote:Still memory leaking.

how do you have this memory leak? do you use internal codec or ffmpeg?

Ffmpeg.

jadO wrote:

xnview wrote:

jadO wrote:Still memory leaking.

how do you have this memory leak? do you use internal codec or ffmpeg?

Ffmpeg.

but which function do you use?

xnview wrote:

jadO wrote:

xnview wrote: how do you have this memory leak? do you use internal codec or ffmpeg?

Ffmpeg.

but which function do you use?

Browser view with setting thumbnailing for entire folder.

Just in case you don't remember: The problem is, that XnviewMP tries to load every file into memory to create thumbnails.
This attempt must fail as XnviewMP has no idea how many files exist and keeps loading and loading until it runs of memory and crashes.
When I use browser view and scroll through the files, XnviewMP creates thumbnails one after another without running out of memory.
So to create thumbnails for whole folder, XnviewMP has to simulate that process: Load files into memory but release them after thumbnail has been created to load new files.

Edit: In fact thumbnailing should be a lightweight background process.

jadO wrote:Just in case you don't remember: The problem is, that XnviewMP tries to load every file into memory to create thumbnails.
This attempt must fail as XnviewMP has no idea how many files exist and keeps loading and loading until it runs of memory and crashes.
When I use browser view and scroll through the files, XnviewMP creates thumbnails one after another without running out of memory.
So to create thumbnails for whole folder, XnviewMP has to simulate that process: Load files into memory but release them after thumbnail has been created to load new files.

Edit: In fact thumbnailing should be a lightweight background process.

Any news on this?

jadO wrote:Just in case you don't remember: The problem is, that XnviewMP tries to load every file into memory to create thumbnails.
This attempt must fail as XnviewMP has no idea how many files exist and keeps loading and loading until it runs of memory and crashes.
When I use browser view and scroll through the files, XnviewMP creates thumbnails one after another without running out of memory.
So to create thumbnails for whole folder, XnviewMP has to simulate that process: Load files into memory but release them after thumbnail has been created to load new files.

It's not a memory leak like previous problem, only that all thumbnails take all memory because currently they are ALL in memory...

xnview wrote:It's not a memory leak like previous problem, only that all thumbnails take all memory because currently they are ALL in memory...

So it is a memory leak by design? How can this be changed? I mean first of all I don't see any sense in loading all files/thumbnails into memore. This MUST result in memory issues. Also a good design for thumbnailing whole folder would be a background process with low cpu and memory footprint so that XnviewMP still can be used at the same time.