NativeScript 5 - iOS Out of memory crash and memory leaks












0














Copy here: https://github.com/NativeScript/NativeScript/issues/6607



Stack:




  • tns 5


  • angular 7



Demo repository:



https://github.com/reposooo/ns-out-of-memory



based on similar issue in ns3: https://github.com/NativeScript/NativeScript/issues/4490



Steps to reproduce (the same results with AOT):




tns run ios




should open app




  • open memory report in Xcode

  • click to example loop 2-4 times

  • click to loop 10x


Reserved memory hasnt gone










share|improve this question




















  • 1




    Have you confirmed that ngOnInit is only ever called once? It looks to me like it should be called every time you show that screen again, which creates more and more subscribers, each of which is referencing this strongly instead of using WeakRef.
    – Ian MacDonald
    Nov 23 '18 at 18:04










  • Its already answers in the issue above. - github.com/NativeScript/NativeScript/issues/6607
    – Dimitar Tachev
    Nov 27 '18 at 9:01


















0














Copy here: https://github.com/NativeScript/NativeScript/issues/6607



Stack:




  • tns 5


  • angular 7



Demo repository:



https://github.com/reposooo/ns-out-of-memory



based on similar issue in ns3: https://github.com/NativeScript/NativeScript/issues/4490



Steps to reproduce (the same results with AOT):




tns run ios




should open app




  • open memory report in Xcode

  • click to example loop 2-4 times

  • click to loop 10x


Reserved memory hasnt gone










share|improve this question




















  • 1




    Have you confirmed that ngOnInit is only ever called once? It looks to me like it should be called every time you show that screen again, which creates more and more subscribers, each of which is referencing this strongly instead of using WeakRef.
    – Ian MacDonald
    Nov 23 '18 at 18:04










  • Its already answers in the issue above. - github.com/NativeScript/NativeScript/issues/6607
    – Dimitar Tachev
    Nov 27 '18 at 9:01
















0












0








0







Copy here: https://github.com/NativeScript/NativeScript/issues/6607



Stack:




  • tns 5


  • angular 7



Demo repository:



https://github.com/reposooo/ns-out-of-memory



based on similar issue in ns3: https://github.com/NativeScript/NativeScript/issues/4490



Steps to reproduce (the same results with AOT):




tns run ios




should open app




  • open memory report in Xcode

  • click to example loop 2-4 times

  • click to loop 10x


Reserved memory hasnt gone










share|improve this question















Copy here: https://github.com/NativeScript/NativeScript/issues/6607



Stack:




  • tns 5


  • angular 7



Demo repository:



https://github.com/reposooo/ns-out-of-memory



based on similar issue in ns3: https://github.com/NativeScript/NativeScript/issues/4490



Steps to reproduce (the same results with AOT):




tns run ios




should open app




  • open memory report in Xcode

  • click to example loop 2-4 times

  • click to loop 10x


Reserved memory hasnt gone







angular nativescript angular2-nativescript angular7 nativescript-angular






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 2 '18 at 10:33









Goncalo Peres

1,3261318




1,3261318










asked Nov 23 '18 at 17:55









dev dev

264




264








  • 1




    Have you confirmed that ngOnInit is only ever called once? It looks to me like it should be called every time you show that screen again, which creates more and more subscribers, each of which is referencing this strongly instead of using WeakRef.
    – Ian MacDonald
    Nov 23 '18 at 18:04










  • Its already answers in the issue above. - github.com/NativeScript/NativeScript/issues/6607
    – Dimitar Tachev
    Nov 27 '18 at 9:01
















  • 1




    Have you confirmed that ngOnInit is only ever called once? It looks to me like it should be called every time you show that screen again, which creates more and more subscribers, each of which is referencing this strongly instead of using WeakRef.
    – Ian MacDonald
    Nov 23 '18 at 18:04










  • Its already answers in the issue above. - github.com/NativeScript/NativeScript/issues/6607
    – Dimitar Tachev
    Nov 27 '18 at 9:01










1




1




Have you confirmed that ngOnInit is only ever called once? It looks to me like it should be called every time you show that screen again, which creates more and more subscribers, each of which is referencing this strongly instead of using WeakRef.
– Ian MacDonald
Nov 23 '18 at 18:04




Have you confirmed that ngOnInit is only ever called once? It looks to me like it should be called every time you show that screen again, which creates more and more subscribers, each of which is referencing this strongly instead of using WeakRef.
– Ian MacDonald
Nov 23 '18 at 18:04












Its already answers in the issue above. - github.com/NativeScript/NativeScript/issues/6607
– Dimitar Tachev
Nov 27 '18 at 9:01






Its already answers in the issue above. - github.com/NativeScript/NativeScript/issues/6607
– Dimitar Tachev
Nov 27 '18 at 9:01














1 Answer
1






active

oldest

votes


















1














Thank you for the report. We have responded in the GitHub issue and the problem is fixed and will be released with {N} iOS Runtime version 5.0.1.






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53451128%2fnativescript-5-ios-out-of-memory-crash-and-memory-leaks%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Thank you for the report. We have responded in the GitHub issue and the problem is fixed and will be released with {N} iOS Runtime version 5.0.1.






    share|improve this answer


























      1














      Thank you for the report. We have responded in the GitHub issue and the problem is fixed and will be released with {N} iOS Runtime version 5.0.1.






      share|improve this answer
























        1












        1








        1






        Thank you for the report. We have responded in the GitHub issue and the problem is fixed and will be released with {N} iOS Runtime version 5.0.1.






        share|improve this answer












        Thank you for the report. We have responded in the GitHub issue and the problem is fixed and will be released with {N} iOS Runtime version 5.0.1.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 27 '18 at 9:04









        Martin Bektchiev

        1463




        1463






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53451128%2fnativescript-5-ios-out-of-memory-crash-and-memory-leaks%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

            Calculate evaluation metrics using cross_val_predict sklearn

            Insert data from modal to MySQL (multiple modal on website)