by jadO (Posted Mon Nov 07, 2016 11:36 am)
Unfortunately not. Examining the functions a lot of strange stuff showed up.
Prerequisites: 4 thumbnails enabled and ffmpeg, all files have been thumbnailed already thumbnailed with non ffmpeg from previous versions.
Now with setting "Create thumbnails for whole folder" off memory footprint starts small. However whith scrolling down it increases. I stopped when it hit >1 Gb.
The same behavior can be seen when turning "Create thumbnails for whole folder" on: Memory increases automatically until > 1Gb and at some point XnViewMP acts weird again
From this behavior it seems to be safe to assume that while creating thumbnails, XnViewMP is loading or trying to load all existing thumbnails into memory. I don't see any reason for this behavior unless they need to be displayed in Explorer.
Second finding: When using the rebuild function via catalog I had a crash during creation and after restarting the application all existing thumbnails from that folder were gone. I chose another folder with existing thumbnails and clicked "Abort" button during recreation only to find that all existing thumbnails from that folder were gone too. It seems that XnViewMP deletes all existing thumbnails before recreation so there are no thumbnails it can try to load. This would explain why the memory footprint remains small using this fucntion.
But this also means that I cannot use it..
Another thing I was missing in the catalog setting is to remove non-existent paths. I was not sure about the "optimize" button. I think I remember that it tends to break everything or removed all categories and tags or something.
So maybe Pierre wanna check if my findings are accurate: 1. Thumbnailing via catalog settings deletes all existing thumbnails from selected folder before thumbnailing starts. In case of crash or aborting all existing thumbnails are lost.
2. In explorer view XnViewMP tries to load all existing thumbnails into memory before or while thumbnailing and probably never releases then which causes memory shortage.
Read Main Topic
helmut wrote:Did the creation of thumbnails described above work without problems, jadO?
Unfortunately not. Examining the functions a lot of strange stuff showed up.
Prerequisites: 4 thumbnails enabled and ffmpeg, all files have been thumbnailed already thumbnailed with non ffmpeg from previous versions.
Now with setting "Create thumbnails for whole folder" off memory footprint starts small. However whith scrolling down it increases. I stopped when it hit >1 Gb.
The same behavior can be seen when turning "Create thumbnails for whole folder" on: Memory increases automatically until > 1Gb and at some point XnViewMP acts weird again
From this behavior it seems to be safe to assume that while creating thumbnails, XnViewMP is loading or trying to load all existing thumbnails into memory. I don't see any reason for this behavior unless they need to be displayed in Explorer.
Second finding: When using the rebuild function via catalog I had a crash during creation and after restarting the application all existing thumbnails from that folder were gone. I chose another folder with existing thumbnails and clicked "Abort" button during recreation only to find that all existing thumbnails from that folder were gone too. It seems that XnViewMP deletes all existing thumbnails before recreation so there are no thumbnails it can try to load. This would explain why the memory footprint remains small using this fucntion.
But this also means that I cannot use it..
Another thing I was missing in the catalog setting is to remove non-existent paths. I was not sure about the "optimize" button. I think I remember that it tends to break everything or removed all categories and tags or something.
So maybe Pierre wanna check if my findings are accurate: 1. Thumbnailing via catalog settings deletes all existing thumbnails from selected folder before thumbnailing starts. In case of crash or aborting all existing thumbnails are lost.
2. In explorer view XnViewMP tries to load all existing thumbnails into memory before or while thumbnailing and probably never releases then which causes memory shortage.
Read Main Topic