NativeScript / NativeScript/ios

Memory Leak on Page Navigation on NS7

Abierto
#107 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
JavaScript
Estrellas
150
Forks
43
Merge medio
3 d 10 h
PR fusionados (30 d)
22

Descripción

Environment

"@nativescript/core": "7.3.0"

"nativescript-vue": "^2.8.1"

"@nativescript/ios": "7.2.0"

✔ Component nativescript has 7.2.1 version and is up to date.

✔ Component @nativescript/core has 7.3.0 version and is up to date.

✔ Component @nativescript/ios has 7.2.0 version and is up to date.

Describe the bug

NS is not freeing memory on page navigations on iOS. When profiling, on each page navigation, the memory increases and app gets slower until, at some point, the app freezes or the OS terminates the app. This behaviour is restricted to IOS, we have profiled with the Android Runtime (https://github.com/NativeScript/android-runtime) and the garbage collection works as expected.

On a very simple application, two included below, each page navigation increases the memory footprint of the app by 60 - 80 megs until the app reaches 1 - 2 Gigs and stops working. If we have a complex page, with some images, and scroll on a list then the memory increases in small iterations but once we navigate to a new page, the memory jumps by 60 - 80 megs.

We have created several test apps with Vue and Angular and the memory leak occurs irrespective of the JS framework.

Solutions Tried and Reviewed
  1. The same issues has been posted previously - Memory Leak on 7.2.0 with (https://github.com/NativeScript/ns-v8ios-runtime)
    https://github.com/NativeScript/ns-v8ios-runtime/issues/105

    We have also:

    EnableProdMode: Is there something similar to enable prod mode on Vue
    https://github.com/NativeScript/nativescript-angular/issues/1215
    Markingmode: https://nativescript.org/blog/markingmode-none-is-official-boost-android-performance-while-avoiding-memory-issues/

  2. Downgraded Nativescript iOSCore to 6.5.4 (https://github.com/NativeScript/ios-runtime).

    We experience the same issues with the older runtime.

  3. Manually destroyed the component - tried different call backs (Unloaded for example)
    https://github.com/nstudio/nativescript-videoplayer/issues/129

  4. Tried with Angular (its happening even on the creation project templates)

  5. Tried with the templates project with 6.5.4

  6. Set the V8flags in the config for IOS (on the V8 Runtime https://github.com/NativeScript/ns-v8ios-runtime)

  7. Navigating with the clearHistory flag (set to true) and navigateBack method = same result

  8. Tested on simulators and real iPhones. (iOS 12.4.8, iOS 13.1, 13.3.1)

  9. Tested with different Layouts (complex and simple)

  10. Manually calling the GC in the navigate back method reduces the memory by a small percentage (0.1% - 0.3%).

  11. As mentioned, it works on Android, see the profiling from below.
    android memory metrics

Project Examples

We include two sample projects, the first is NS7 and the second NS6, both exhibit the same issues with memory.

NS7: https://github.com/alkimiiapps/memoryleakexample

NS6: https://github.com/alkimiiapps/ns6test

Example Video of the memory reaching 0.5 Gig

Here is a gif of the profiling, where the user navigates back and forth between pages and the memory increases with each navigation.

IMAGE ALT TEXT HERE

Guía de contribución

Abrir la guía de contribución

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.

Línea de trabajo

Empieza reproduciendo la fuga con los proyectos de ejemplo NS7 y NS6 enlazados, después crea un perfil de la navegación repetida entre páginas en iOS y compara el comportamiento con Android. El issue se completa cuando se identifica el origen de la memoria retenida y la navegación deja de provocar el crecimiento de memoria reportado o el bloqueo eventual.

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

Evaluación

Stack tecnológico
ios, javascript
Área
mobile-dev, performance
Tipo de issue
Error
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
20/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.