github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-11 20:54:58 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

High RAM Usage #112

New Issue
Closed
opened 2025-11-07 08:26:56 -06:00 by GiteaMirror · 12 comments
GiteaMirror commented 2025-11-07 08:26:56 -06:00
Owner
Copy Link

Originally created by @ryanleesipes on GitHub (Nov 4, 2017).

Two services from Bitwarden appear to be using a lot of RAM, total they represent about 500MB when the app isn't even being used (assume this is for autofill).

I will reinstall the app at some point and see if I can add the specific services, but I removed it and suddenly my phone was running a ton better (on a Samsung Galaxy S8).

Originally created by @ryanleesipes on GitHub (Nov 4, 2017). Two services from Bitwarden appear to be using a lot of RAM, total they represent about 500MB when the app isn't even being used (assume this is for autofill). I will reinstall the app at some point and see if I can add the specific services, but I removed it and suddenly my phone was running a ton better (on a Samsung Galaxy S8).
GiteaMirror commented 2025-11-07 08:26:57 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 4, 2017):

Hm. That's odd. Maybe there was some runaway process going since normal usage should linger below 100mb.

@kspearrin commented on GitHub (Nov 4, 2017): Hm. That's odd. Maybe there was some runaway process going since normal usage should linger below 100mb.
GiteaMirror commented 2025-11-07 08:26:57 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 4, 2017):

Try disabling the autofill service for a bit and see if that is the cause.

@kspearrin commented on GitHub (Nov 4, 2017): Try disabling the autofill service for a bit and see if that is the cause.
GiteaMirror commented 2025-11-07 08:26:58 -06:00
Author
Owner
Copy Link

@bashfulrobot commented on GitHub (Nov 4, 2017):

I'm just adding a comment here to follow this thread. Had some discussion on Twitter... I'm experiencing similar issues. I have a memory monitor running... And I'm trying to gather some metrics.

With client:
Memory utilization starts out around 60%... But then does a slow climb up towards 80%-86%

Without client:

Memory utilization sits around 46%. Then does a slow climb to about 51% and settles. But I just uninstalled so I don't think this conclusion means a whole lot yet. I need to monitor it for a little longer.

One thing to note is that I did have autofill enabled. After I get far enough in to make some sort of conclusion without the client... I will add it back in and disable the autofill service and see where that compares. Will post back at a later time.

@bashfulrobot commented on GitHub (Nov 4, 2017): I'm just adding a comment here to follow this thread. Had some discussion on Twitter... I'm experiencing similar issues. I have a memory monitor running... And I'm trying to gather some metrics. With client: Memory utilization starts out around 60%... But then does a slow climb up towards 80%-86% Without client: Memory utilization sits around 46%. Then does a slow climb to about 51% and settles. But I just uninstalled so I don't think this conclusion means a whole lot yet. I need to monitor it for a little longer. One thing to note is that I did have autofill enabled. After I get far enough in to make some sort of conclusion without the client... I will add it back in and disable the autofill service and see where that compares. Will post back at a later time.
GiteaMirror commented 2025-11-07 08:26:58 -06:00
Author
Owner
Copy Link

@ryanleesipes commented on GitHub (Nov 4, 2017):

@kspearrin will do.

@ryanleesipes commented on GitHub (Nov 4, 2017): @kspearrin will do.
GiteaMirror commented 2025-11-07 08:26:58 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 4, 2017):

I’ll try running some tests on my nexus 5x today and see if I can reproduce anything. Right now I’m sitting at 112mb with the autofill service running.

@kspearrin commented on GitHub (Nov 4, 2017): I’ll try running some tests on my nexus 5x today and see if I can reproduce anything. Right now I’m sitting at 112mb with the autofill service running.
GiteaMirror commented 2025-11-07 08:26:59 -06:00
Author
Owner
Copy Link

@bashfulrobot commented on GitHub (Nov 4, 2017):

One clarification on my use case... I had been monitoring % utilization, and had not been monitoring the amount of RAM used.

For reference, this is on a pixel 1. (4gb ram)

@bashfulrobot commented on GitHub (Nov 4, 2017): One clarification on my use case... I had been monitoring % utilization, and had not been monitoring the amount of RAM used. For reference, this is on a pixel 1. (4gb ram)
GiteaMirror commented 2025-11-07 08:26:59 -06:00
Author
Owner
Copy Link

@ryanleesipes commented on GitHub (Nov 4, 2017):

Without autofill, it is sitting around 97.54mb for Bitwarden "AndroidPushService"

@ryanleesipes commented on GitHub (Nov 4, 2017): Without autofill, it is sitting around 97.54mb for Bitwarden "AndroidPushService"
GiteaMirror commented 2025-11-07 08:27:00 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 4, 2017):

Looking at the exact amount will be better. Also worth noting are the few other autofill options under Settings -> Features. You could try those to see if they change anything as well.

@kspearrin commented on GitHub (Nov 4, 2017): Looking at the exact amount will be better. Also worth noting are the few other autofill options under Settings -> Features. You could try those to see if they change anything as well.
GiteaMirror commented 2025-11-07 08:27:00 -06:00
Author
Owner
Copy Link

@bashfulrobot commented on GitHub (Nov 4, 2017):

Ok, sounds good. I also enabled the dev mode on my device and will stay monitoring my actual ram consumption as well.

@bashfulrobot commented on GitHub (Nov 4, 2017): Ok, sounds good. I also enabled the dev mode on my device and will stay monitoring my actual ram consumption as well.
GiteaMirror commented 2025-11-07 08:27:00 -06:00
Author
Owner
Copy Link

@bashfulrobot commented on GitHub (Nov 4, 2017):

Ok, since adding the app back on, I no longer reproduce. Utilization remains higher, but consumed remains at around 80-105mb. So if that is normal, I might be good now.

@bashfulrobot commented on GitHub (Nov 4, 2017): Ok, since adding the app back on, I no longer reproduce. Utilization remains higher, but consumed remains at around 80-105mb. So if that is normal, I might be good now.
GiteaMirror commented 2025-11-07 08:27:01 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Nov 22, 2017):

Any verdict here?

@kspearrin commented on GitHub (Nov 22, 2017): Any verdict here?
GiteaMirror commented 2025-11-07 08:27:01 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Dec 5, 2017):

Closing since there was no further information.

@kspearrin commented on GitHub (Dec 5, 2017): Closing since there was no further information.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#112
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?