Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android app startup performance slow #42

Closed
sreich mannequin opened this issue Feb 13, 2017 · 9 comments
Closed

Android app startup performance slow #42

sreich mannequin opened this issue Feb 13, 2017 · 9 comments

Comments

@sreich
Copy link
Mannequin

sreich mannequin commented Feb 13, 2017

Android startup performance is much slower than lastpass, which I thought was slow in itself.

A cold start is much slower than a cold start of lastpass, and a hot start of lastpass is about 2 seconds.

A hot start of bitwarden is 3-6 seconds. Obviously this isn't a benchmark and you and I know the many variables in the system, but I can feel it's significantly slower and too slow when I have to rely on it for logging into everything.

This is on a pixel XL running Android 7.1.2(beta)

This was also with a near empty database, without any locking enabled. Lastpass I think is faster if I didn't have fingerprint enabled.

I'm free to test or debug (like provide logs, etc) if necessary. I can't speak as to if this is a regression or not (I haven't used it significantly since I was waiting on auto fill)

@kspearrin
Copy link
Mannequin

kspearrin mannequin commented Feb 13, 2017

What are you considering as a hot start? It seems mostly instant to me if i background the app and re-open it.

@jerryn70
Copy link
Mannequin

jerryn70 mannequin commented Feb 14, 2017

Sometimes when I click auto fill from notification , the main logo screen of bitwarden shows for more than15 sec then after that it shows the pin screen, but at that time it won't shows the pin keyboard, it will again take about 15 sec to show the pin keyboard

@kspearrin
Copy link
Mannequin

kspearrin mannequin commented Feb 14, 2017

@jerryn70 What are your device details and versions?

@jerryn70
Copy link
Mannequin

jerryn70 mannequin commented Feb 14, 2017

Moto x play
Marshmallow 6.0.1
Non rooted

@kspearrin
Copy link
Mannequin

kspearrin mannequin commented Feb 14, 2017

@jerryn70 I've seen similar behavior once a while back and after I reinstalled the app it went away. I haven't seen it since though. I'll continue to investigate.

@sreich
Copy link
Mannequin Author

sreich mannequin commented Feb 14, 2017

I was referring to hot start as in me being in the app and hitting home, or back to get back to the launcher.

As opposed to swiping the app out of recents which kills the app.

The latter is where the lowest hanging fruit are. Its startup after it is swiped from recents(what I would call a cold start) is quite long (esp when I'm waiting to log into my computer each bathroom break)

I've also noticed it's using about 377 MB of RAM right now..That probably doesn't help things as far as getting memory killed goes. Especially on devices with 1-2gb of RAM.

See http://i.imgur.com/P1PJ4Br.png

I don't know how much of it is in your control or inherent with xamarin.

Although I did find it interesting that this page shows two bitwarden entries.. Which is strange to me, maybe one is the accessibility service(LastPass doesn't have that though)? Or perhaps separate threads?

@kspearrin
Copy link
Mannequin

kspearrin mannequin commented Feb 20, 2017

This should now be resolved with the 491 build in the play store beta.

@kspearrin kspearrin mannequin closed this as completed Feb 20, 2017
@i3130002
Copy link
Mannequin

i3130002 mannequin commented Oct 3, 2022

@sreich Is it a duplicate of #1723 ?

@sreich
Copy link
Mannequin Author

sreich mannequin commented Oct 3, 2022

I wouldn't say so, theirs is more about biometric unlock, this issue was about startup. But, either way this seems to be resolved I don't have any issues with it on my pixel 6a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants