Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Crash after opening from external source #706

Closed
sblatz opened this issue Feb 27, 2019 · 5 comments
Closed

Crash after opening from external source #706

sblatz opened this issue Feb 27, 2019 · 5 comments
Assignees
Labels
b:crash Crashes Fenix: should link to Sentry, Crash-Stats or GPlay info

Comments

@sblatz
Copy link
Contributor

sblatz commented Feb 27, 2019

Steps to reproduce

  1. Navigate to a website from within Fenix
  2. While BrowserFragment is open, close the app
  3. Open a link from an external source (I used Samsung messages)
  4. Press Home
  5. Open the tab you previously opened

Expected behavior

Tab loads normally

Actual behavior

Fenix crashes

Crash log

image

Device information

  • Android device: 8.0.0
  • Fenix version: 1.0.19090 (master)

┆Issue is synchronized with this Jira Task

@sblatz sblatz added the b:crash Crashes Fenix: should link to Sentry, Crash-Stats or GPlay info label Feb 27, 2019
@sblatz sblatz self-assigned this Feb 27, 2019
@sblatz sblatz added this to the Sprint 2-2 (Milestone 2) milestone Feb 27, 2019
@sblatz
Copy link
Contributor Author

sblatz commented Feb 28, 2019

Perhaps related to #575

Looping in @colintheshots on this since he just resolved the issue in #575.

From @colintheshots:

I resolved the recreate on custom tabs issue by not recreating if the theme was already set correctly. It might be a new way to recreate or create two GeckoViews for the same session.

@sblatz
Copy link
Contributor Author

sblatz commented Feb 28, 2019

I confirmed that the activity is not being recreated in this circumstance.

What's odd is that going home, then selecting the newly created tab (that came from an external source) does not cause a crash. This ticket will require more investigation and will likely have to be pushed to next sprint unless someone else can take it over

@sblatz
Copy link
Contributor Author

sblatz commented Mar 4, 2019

It seems like abd0845 initially fixed this, but with the change at cf260e4 the crash returned.

@pocmo any thoughts on this?

@sblatz
Copy link
Contributor Author

sblatz commented Mar 4, 2019

I paired with @boek for a bit. Turns out we needed to make our activity a singleInstance

Basically when we were launching from outside the app, a new HomeActivity was created while still keeping the old one around, which meant bad memory states could happen leading to crashes.
More info here.

sblatz added a commit to sblatz/fenix that referenced this issue Mar 4, 2019
sblatz added a commit to sblatz/fenix that referenced this issue Mar 4, 2019
@ghost ghost added in progress labels Mar 4, 2019
@sblatz sblatz added the size S label Mar 4, 2019
@sblatz
Copy link
Contributor Author

sblatz commented Mar 4, 2019

Note: our incoming patch will also fix an issue where opening from an external app would actually create the activity inside your current app rather than sending you off to Fenix (not a custom tab).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
b:crash Crashes Fenix: should link to Sentry, Crash-Stats or GPlay info
Projects
None yet
Development

No branches or pull requests

3 participants