Nextcloud Apps Crash when Scrolling
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
- 48/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- mobile-dev, performance
Línea de trabajo
Start by reproducing scrolling in a synchronized folder with 8,000+ files on Android 14, then inspect the RecyclerView scrolling and ConstraintLayout measurement path shown in the OutOfMemoryError stack trace. Done means scrolling no longer causes excessive memory growth, lag, or an app crash under the reported conditions.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
⚠️ Before posting ⚠️
- This is a bug, not a question or an enhancement.
- I've searched for similar issues and didn't find a duplicate.
- I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
- I agree to follow Nextcloud's Code of Conduct.
Steps to reproduce
I was just scrolling through my folders looking for a file, then the app started lagging and crashing.
Expected behaviour
Scrolling shouldn't take up much RAM Usage right? It should be optimized further so that the application does not consume too much RAM when scrolling through folders with lots of files.
Actual behaviour
When scrolling through a folder with lots of files, the app may run smoothly for a few seconds, then start to lag and crash.
Android version
14
Device brand and model
Tecno LH8n
Stock or custom OS?
Stock
Nextcloud android app version
34.1.1
Nextcloud server version
33.0.3.2
Using a reverse proxy?
I don't know
Android logs
Cause of error
Exception in thread "main" java.lang.OutOfMemoryError: Failed to allocate a 32 byte allocation with 3819520 free bytes and 3730KB until OOM, target footprint 536870912, growth limit 536870912; giving up on allocation because <1% of heap free after GC.
at java.util.HashMap$KeySet.iterator(HashMap.java:991)
at java.util.HashSet.iterator(HashSet.java:183)
at androidx.constraintlayout.core.widgets.analyzer.Direct.verticalSolvingPass(Direct.java:496)
at androidx.constraintlayout.core.widgets.analyzer.Direct.solvingPass(Direct.java:230)
at androidx.constraintlayout.core.widgets.ConstraintWidgetContainer.layout(ConstraintWidgetContainer.java:711)
at androidx.constraintlayout.core.widgets.analyzer.BasicMeasure.solveLinearSystem(BasicMeasure.java:170)
at androidx.constraintlayout.core.widgets.analyzer.BasicMeasure.solverMeasure(BasicMeasure.java:298)
at androidx.constraintlayout.core.widgets.ConstraintWidgetContainer.measure(ConstraintWidgetContainer.java:119)
at androidx.constraintlayout.widget.ConstraintLayout.resolveSystem(ConstraintLayout.java:1634)
at androidx.constraintlayout.widget.ConstraintLayout.onMeasure(ConstraintLayout.java:1777)
at android.view.View.measure(View.java:27339)
at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:7124)
at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1608)
at android.widget.LinearLayout.measureHorizontal(LinearLayout.java:1240)
at android.widget.LinearLayout.onMeasure(LinearLayout.java:723)
at android.view.View.measure(View.java:27339)
at androidx.recyclerview.widget.RecyclerView$LayoutManager.measureChildWithMargins(RecyclerView.java:10210)
at androidx.recyclerview.widget.LinearLayoutManager.layoutChunk(LinearLayoutManager.java:1688)
at androidx.recyclerview.widget.LinearLayoutManager.fill(LinearLayoutManager.java:1622)
at androidx.recyclerview.widget.LinearLayoutManager.scrollBy(LinearLayoutManager.java:1425)
at androidx.recyclerview.widget.LinearLayoutManager.scrollVerticallyBy(LinearLayoutManager.java:1158)
at androidx.recyclerview.widget.RecyclerView.scrollStep(RecyclerView.java:2050)
at androidx.recyclerview.widget.RecyclerView$ViewFlinger.run(RecyclerView.java:5835)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1506)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1515)
at android.view.Choreographer.doCallbacks(Choreographer.java:1085)
at android.view.Choreographer.doFrame(Choreographer.java:971)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1489)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:243)
at android.os.Looper.loop(Looper.java:338)
at android.app.ActivityThread.main(ActivityThread.java:8470)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:600)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1064)
App information
- ID:
com.nextcloud.client - Version:
340010190 - Build flavor:
gplay
Device information
- Brand:
TECNO - Device:
TECNO-LH8n - Model:
TECNO LH8n - Id:
UP1A.231005.007 - Product:
LH8n-GL
Firmware
- SDK:
34 - Release:
14 - Incremental:
250606V834
Server error logs
Additional information
My folder have 8000+ file and Already Synchronized with my phone
- Lenguaje dominante
- Kotlin
- Estrellas
- 5.7k
- Forks
- 2.1k
- Merge medio
- 1 d 22 h
- PR fusionados (30 d)
- 135
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nextcloud/android
-
0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
nextcloud/android#17845 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[Bug] Lock owned by another client (e.g. Text app) cannot be unlocked from the appPosiblemente ocupada @falkloewert la tomó hace 28 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nextcloud/android#17837 · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
0. Needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
nextcloud/android#17533 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
RC 34.1.0-01: Duplicated wording in creation menu — "New" prefix + creator name produces "New New document" ("Neu Neues Dokument")Posiblemente ocupada @ChristianTannheimer la tomó hace 118 días. Abierto0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
Todos los issues de nextcloud/android
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Kotlin/kotlin-lsp#309 ·
-
Two stored artist rows are not act names: "DJS" from a Renate floor heading and "Stevie Cox -"Abiertoarea:data-quality importer size:S
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
enorm-labs/event-junkie#5136 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Type: Possible bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
spacecowboy/Feeder#1318 ·
Los mantenedores suelen responder en 1 día
-
个人助手回复内容既无法手动选中复制,也没有一键复制Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
wangzan101/Mika#644 ·
Los mantenedores suelen responder en 1 día