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

High memory consumption / paging out the launcher #39

Closed
GoogleCodeExporter opened this issue Mar 15, 2015 · 2 comments
Closed

High memory consumption / paging out the launcher #39

GoogleCodeExporter opened this issue Mar 15, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

After having scanned a few books (>100) I noticed that switching back to
the home screen will show me a "loading..." popup for a while or even a
white screen with the HTC logo.
Looks like BookWorm uses loads of dynamic ram...
No other app (experimenting mostly with navigation stuff and calenders)
triggers this behavior so far.
Not a big issue right now, but might point to inefficient memory handling
or some other architectural problem.


(A bit of a pita when my fumbiling fingers accidentally press BACK instead
of MENU)



Original issue reported on code.google.com by afx...@gmail.com on 8 May 2010 at 11:55

@GoogleCodeExporter
Copy link
Author

I doubt this is because of BookWorm, but I had planned to do more profiling 
anyway, 
and will check into it to be sure. (BookWorm uses the DB, and ListView, so it 
doesn't 
load everything into RAM at once, also it uses the ViewHolder pattern, so it's 
pretty 
good, at least in terms of the recommended practices and stuff I know to do -- 
could 
be something I am missing though, so again, will look into it.)

Original comment by charlie....@gmail.com on 10 May 2010 at 1:32

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

I can't come up with anything while profiling, looks pretty lean for BookWorm 
to me. I'll keep this in mind though, keep an eye out, and re-open if necc. 

Original comment by charlie....@gmail.com on 17 Jun 2010 at 1:14

  • Changed state: WontFix

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

No branches or pull requests

1 participant