View Single Post
Old 08-05-2013, 03:01 PM   #1
Hotrootsoup
Junior Member
Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.Hotrootsoup has never been to obedience school.
 
Posts: 7
Karma: 44444
Join Date: Aug 2013
Device: Kindle Paperwhite (5.3.4 JB)
Questions on memory leaks and exit practices.

According to cowlark,
Quote:
Whenever you load a class containing static members, the memory used for those members will never be freed. Ever.
Is this outdated, or is it really still a problem?

If it is a problem, can someone explain it a little further? Is it just static members I'm setting in the classes I use, or are includes also wasting memory until the kindle is reset? Again, if so, would two apps include-ing the same class cause twice the amount of memory wasted, or is it limited to one per Java class name?

Even supposing that isn't true at all, how do you all shut down your apps? Not necessarily what technique you use to avoid the home button, but how do you clean up? What can I trust the garbage collector with?
Hotrootsoup is offline   Reply With Quote