Closed Bug 1160494 Opened 7 years ago Closed 3 years ago

Logins consumes an excessive amount of memory

Categories

(Firefox for Android Graveyard :: Logins, Passwords and Form Fill, defect, P4)

ARM
Android
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: pwd.mozilla, Unassigned)

References

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150430095850

Steps to reproduce:

It seems to be incredibly memory intensive. Which is surprising given that the extension that provides the same functionality Mobile Password Manager[1] manages to do the same without freeing the entire device.

[2] https://addons.mozilla.org/en-us/firefox/addon/mobile-password-manager/
Blocks: 1121681
OS: Unspecified → Android
Hardware: Unspecified → ARM
Summary: Opening Logins brings whole system to its knees → Logins consumed an excessive amount of memory
Summary: Logins consumed an excessive amount of memory → Logins consumes an excessive amount of memory
When looking at the profile using WebIDE, I don't see any large jump in memory usage. I have ~150 passwords. It takes ~ 1sec to display the list.

Can you post logs, or something else, to give some insight into why you think memory usage is extreme?
Blocks: mobile-about-passwords
No longer blocks: 1121681
Normally memory usage is ~350mb when opening logins it shoots up to ~450mb
Bill and I set P4
Priority: -- → P4
My guess is that we're witnessing jank and memory usage from loading all the favicons.  Locally, this causes pain for me.
Things have improved dramatically here. I think we can mitigate many of the remaining performance issues here by simply removing the search filter and relying on "Find in Page"
Hi Paul,

Is this issue still reproducible?

Thank you!
Flags: needinfo?(pwd.mozilla)
This is actually decent now.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(pwd.mozilla)
Resolution: --- → INVALID
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.