Folder view freezes with large amount of images and does not respond to taps

Abierto
  • ¿Algo no está bien?
#1,092 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
32/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
android, kotlin
Área
mobile, performance

Línea de trabajo

The payload names no source files, tests or entry points, so the first step is reproducing the freeze with a large folder tree of thousands of images. Profile what runs on the main thread when a folder is tapped and when swipe-to-refresh runs, then find which work scales with total collection size rather than with the visible items. Done means a folder opens promptly on a collection of about 30,000 images, and a tap is accepted while the refresh is still running.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug needs triage
Checklist
  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.
Affected app version

1.13.1

Affected Android/Custom ROM version

Android 16/OxygenOS 16

Affected device model

Oneplus Nord 5

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

  1. Have a very large photo collection on your phone (mine has 30 000 photos, 1200px wide webp pics, average file size maybe 90kB) somewhere where Fossify Gallery can access it (e.g. sdcard/Pictures/COLLECTION or sdcard/Pictures2/COLLECTION2), that have been divided to subfolder tree structure of hundreds of folders.

  2. Open fossify gallery

  3. Tap any visible folder to open it

Expected behavior

Folder opens

Actual behavior

Most of time there is no response to tap. Sometimes there is response with 5 sec delay, sometimes with over 20 sec delay. Sometimes but much more rarely it opens near instantly.

Screenshots/Screen recordings

No response

Additional information

I have replicated this behaviour with at least 2 different devices (Oneplus Nord 5, android 16 and Samsung Galaxy S21FE android 14).

I suspect reason being that devs have maybe? not thought about users having this large collections and have not optimized the UI with the thought that there could be so large amount of pics and possibly assume that whole UI (instead of just the visible portion) should be rendered to some degree before it can accept taps.

Nevertheless having minor versions of images of your whole photo collection on your phone is very useful if/whenever you feel sharing some memories from past.

Whatever is the case the app is currently pretty unusable for me as virtually any time I open it (unless I open an individual file from file manager app which I sometimes also do) it does not respond properly before a long delay.

A related issue could be that if I swipe down to refresh UI (sometimes I also do it half accidentally). It pretty much freezes the app as it starts the whole rendering process from scratch and seems to go through whole photo collection again. So also this feature should have some mechanism that taps / some sort of usage is already possible for viewable area before the whole thing is re-rendered again.

Lenguaje dominante
Kotlin
Estrellas
3.8k
Forks
270
Merge medio
1 d 18 h
PR fusionados (30 d)
14

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de FossifyOrg/Gallery

Todos los issues de FossifyOrg/Gallery

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.