I had been wondering if the fixed leaks were also causing the OOM issues reported by you, jadO.jadO wrote:I don't understand what you are trying to say.xnview wrote:it's only for create catalog in settings
Thanks for clarifying, Pierre.
Moderators: XnTriq, helmut, xnview
I had been wondering if the fixed leaks were also causing the OOM issues reported by you, jadO.jadO wrote:I don't understand what you are trying to say.xnview wrote:it's only for create catalog in settings
The problem fixed is when you 'add folder' in catalog settingjadO wrote:I don't understand what you are trying to say.
how do you have this memory leak? do you use internal codec or ffmpeg?jadO wrote:Still memory leaking.
Ffmpeg.xnview wrote:how do you have this memory leak? do you use internal codec or ffmpeg?jadO wrote:Still memory leaking.
but which function do you use?jadO wrote:Ffmpeg.xnview wrote:how do you have this memory leak? do you use internal codec or ffmpeg?jadO wrote:Still memory leaking.
Browser view with setting thumbnailing for entire folder.xnview wrote:but which function do you use?jadO wrote:Ffmpeg.xnview wrote: how do you have this memory leak? do you use internal codec or ffmpeg?
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.
It's not a memory leak like previous problem, only that all thumbnails take all memory because currently they are ALL in memory...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.
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.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...