You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discovered a problem with the Piwigo app that comes up when you scroll through larger categories.
It seems like all the Thumbnails that have been loaded while scrolling are kept in memory. At some time, the device runs out of memory and the app crashes.
Depending on the thumbnail-quality setting and the available memory, you're experiencing the impact of the high memory consumption after approx. 400 loaded thumbnails.
Is there a way to unload passed thumbnails on demand, similar to loading but in reverse? I mean something like:
When you scroll down, the app loads the next 500 thumbnails below and unloads all above.
When you scroll up, the app loads the previous 500 thumbnails above und unloads all below.
To keep the scrolling position, you could preserve the images dimensions and clear its contents only. Just as a suggestion.
I would classify this one as a bug.
Best regards
Sven
The text was updated successfully, but these errors were encountered:
Hi again,
hope you're doing well.
I discovered a problem with the Piwigo app that comes up when you scroll through larger categories.
It seems like all the Thumbnails that have been loaded while scrolling are kept in memory. At some time, the device runs out of memory and the app crashes.
Depending on the thumbnail-quality setting and the available memory, you're experiencing the impact of the high memory consumption after approx. 400 loaded thumbnails.
Is there a way to unload passed thumbnails on demand, similar to loading but in reverse? I mean something like:
When you scroll down, the app loads the next 500 thumbnails below and unloads all above.
When you scroll up, the app loads the previous 500 thumbnails above und unloads all below.
To keep the scrolling position, you could preserve the images dimensions and clear its contents only. Just as a suggestion.
I would classify this one as a bug.
Best regards
Sven
The text was updated successfully, but these errors were encountered: