Closed Bug 902060 Opened 12 years ago Closed 5 years ago

GeckoProfile shouldn't be cached on the Activity

Categories

(Firefox for Android Graveyard :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: wesj, Unassigned)

Details

We currently store a cached GeckoProfile for the current profile on GeckoApp. GeckoApp's lifecycle and Gecko's lifecycle aren't the same though, meaning this profile can be destroyed while Gecko lives on. We should cache GeckoProfile on the Application instead.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Are you sure this is a dupe? I thought this bug was about the fact that we hold onto the profile in GeckoApp and then reference it elsewhere (http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/GeckoProfile.java#72). Bug 937945 won't fix this.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Status: REOPENED → NEW
Hmm... you're right. I know a filed a bug for 937945, and thought from the title this was it :)
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 12 years ago5 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.