Skip to content

Frame crashes on app restore occasionally  #715

Closed

Description

@sitefinitysteve

If I leave my app open, then come back to it later it crashes with this??

https://goo.gl/photos/Z8pJyrY8w8nNM9Uf6

... It's always done this

Activity

  1. Kamilius commented on Sep 12, 2015

    @Kamilius

    I have exactly the same issue on Android.

    • App is running
    • I'm pressing "home" button to suspend it
    • Opening Chrome and navigating to any page
    • Opening app manager
    • Choosing running NS application
    • Getting error screen with a stack trace:
      quickmemo _2015-09-12-11-00-12

    Sadly I don't know how to copy a full stack trace in this situation.
    @sitefinitysteve gave only screenshot of first lines of actual stacktrace part of this log.

    Funny thing, that it is hard to reproduce if you simply suspending app, without running different ones. For example, If I'm locking/unlocking phone or simply navigating it, mostly - everything's great. But when it comes to launching different apps - it crashes with error above.

    When I've tried to debug it using node-inspector and placing a callbacks for all App Events except already handled suspend/resume, node-inspector is simply detaching somewhere upon 'Chrome' step described above.

    Any clues on how to copy a full stack trace or fixing this issue?

    I'm using nativescript-cli on Ubuntu 14.04 with real device.

  2. sitefinitysteve commented on Sep 14, 2015

    @sitefinitysteve
    ContributorAuthor

    I am unable to replicate via those steps 100% of the time, however I did try to get a full stack trace by using the app analytics module of the telerik platform...app crashed twice on a demo, nothing logged.

    application.on(application.uncaughtErrorEvent, function (args) {
        var exception;
    
        if (args.android)
            exception = args.android;
        else if (args.ios)
            exception = args.ios;
    
        monitor.trackException(exception, "Uncaught exception");
    });
    
  3. x4080 commented on Sep 30, 2015

    @x4080

    I think I have a way to replicate the situation ,in the developers option , set background process limit to 2 or 1, open ns app , go to another app or two then go to the ns app. If the ns app is restarted it will crash as the above picture ( using real device here )

  4. Kamilius commented on Oct 1, 2015

    @Kamilius

    @x4080 👍 awesome. It really was crashing upon app restart. Didn't knew that on android dev options is such option, like limiting processes.

    And that actually works 100% of time

    Also, I think that this situation should've been able to be handled by at least - "lowMemory" or "uncaughtError" application events, but it's not.

  5. x4080 commented on Oct 1, 2015

    @x4080

    Glad it can help a bit..the Google search and stackoverflow talked about manifest app name setting but i still cannot resolve it. Maybe other people csn help

  6. AntonioCuevaUrraco commented on Oct 9, 2015

    @AntonioCuevaUrraco

    +1 I would love to figure out a way to solve this issue as it is happening quite often.

  7. x4080 commented on Oct 9, 2015

    @x4080

    I think it needs high priority also

  8. added this to the milestone on Oct 9, 2015
  9. blagoev commented on Oct 9, 2015

    @blagoev
    Contributor

    raised the priority. We will investigate this further as part of 1.5 work.

  10. x4080 commented on Oct 9, 2015

    @x4080

    Thanks man

  11. x4080 commented on Oct 11, 2015

    @x4080

    I think the problem is in frame.android.ts (PageFragmentBody), android complains about the constructor is not public and have no empty constructor, I tried to change the constructor without parameters and calling new PageFragmentBody with :

        var newFragment = new PageFragmentBody();
        newFragment.frame = this;
        newFragment.entry = backstackEntry;
    

    (the constructor) :

    class PageFragmentBody extends android.app.Fragment {
    public frame: Frame;
    public entry: definition.BackstackEntry;
    
    public  constructor() {
        super();
        return global.__native(this);
    }
    

    It still the same result, maybe because class generated is not public ? How can we make inherited class in nativescript public ?

  12. 5 remaining items

  13. lscown commented on Nov 5, 2015

    @lscown

    Any update on this?

  14. hshristov commented on Nov 6, 2015

    @hshristov
    Contributor

    Hi guys,

    We have fixed this issue and it will be included in 1.6 release.

  15. added
    ready for testTSC needs to test this and confirm against live production apps and automated test suites
    and removed on Nov 6, 2015
  16. x4080 commented on Nov 6, 2015

    @x4080

    Thumbs up..1.5 already finished?

  17. sitefinitysteve commented on Nov 6, 2015

    @sitefinitysteve
    ContributorAuthor

    @hshristov Yeah is this a typo? Did you mean 1.5? I see the version has been incrimented to 1.5, but this is a pretty critical bug to push back to December or later.

  18. hshristov commented on Nov 9, 2015

    @hshristov
    Contributor

    @sitefinitysteve Yeah typo on my side. Sorry. I meant 1.5

  19. added and removed
    ready for testTSC needs to test this and confirm against live production apps and automated test suites
    on Nov 13, 2015
  20. lock commented on Aug 30, 2019

    @lock

    This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

  21. locked and limited conversation to collaborators on Aug 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions