NativeScript / NativeScript/ios
Navigate Memory Problem
Nessuno ha ancora preso questa issue.
- Lingua principale
- JavaScript
- Stelle
- 150
- Fork
- 43
- Merge medio
- 3g 10h
- PR unite (30g)
- 22
Descrizione
I am running into a reproducible memory leak that occurs when navigating to another page.
In my example we navigate with a 1 second timeout to the same page in an endless loop.
Example Repository:
https://github.com/atabix/nativescript-memory-leak-example
➜ nativescript -v
7.2.0
Use Case 1
Run the app with all of the same dependencies with one exception:
@nativescript/ios@6.5.4
Allow the app to run for a period of thirty minutes.
Use Case 2
Run the app with all of the same dependencies with one exception:
@nativescript/ios@7.2.0
Allow the app to run for a period of thirty minutes.
Results
The app starts around ~74MB in both uses cases. In this first couple of minutes the app slowly increases in total memory used, incrementing about 1MB every couple of seconds.
After this initial period the memory seems to stabilize at around 93MB.
The same test has been applied to two very different apps in production with pages that are more complex. This example here resulted in 1MB increments. The production apps resulted in 50MB increments (starting at 146MB and eventually reaching 2GB). In combination with navigating between different kinds of pages this memory problem is compounded, eventually resulting in the app shutting itself down.
This behavior remained consistent when manually calling Utils.GC() and using clearHistory: true on navigation. These two seemed to have no affect on the outcome of the results.
Honorable mention
The issue was first discovered in a project using nativescript-vue. The funny thing is that the amount of memory in each increment used is less than vanilla NativeScript. To remove nativescript-vue as a variable the above uses cases have taken place without it.
References
https://github.com/NativeScript/NativeScript/issues/6890
- Manual garbage collection doesn't resolve the issue.
https://github.com/NativeScript/nativescript-angular/issues/1215
- The issue seems to be with Angular. A similar approach was attempted for NativeScript Vue by hooking into the destroy method of Vue components; however, as mentioned above, Vue doesn't seem to be a factor in this problem.
https://github.com/NativeScript/ns-v8ios-runtime/issues/100
- This is currently an issue in the v7.2.0 iOS runtime. Perhaps it may also be affecting other factors of NativeScript?
I am currently at a loss as to how to proceed. The issue is extremely significant in any pages that display more than a single button and some text. It's only apparent in apps where people navigate between pages a lot for an extended period of time.
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia dal repository collegato atabix/nativescript-memory-leak-example e riproduci il suo ciclo di navigazione alla stessa pagina ogni secondo per 30 minuti con @nativescript/ios 6.5.4 e 7.2.0. Leggi le issue di NativeScript, nativescript-angular e ns-v8ios-runtime a cui si fa riferimento mentre profili la memoria; il lavoro è completato quando la perdita è isolata e il test di navigazione non mostra più la crescita segnalata.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- ios, javascript
- Ambito
- mobile-dev, performance
- Tipo di issue
- Bug
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 25/100