1. Check out our app, Forums for Android! Download and leave feedback here!

Support Definite Memory Leak

Discussion in 'Android Devices' started by ghamden, Jul 24, 2010.

  1. ghamden

    ghamden Well-Known Member
    Thread Starter
    38

    Jul 10, 2010
    101
    14
    38
    Definite Memory Leak

    Rooted Most bloatware removed also Using ATK memory starts around 280 i have atk set hourly memory leaks to around 170 atk runs brings it back to around 200 withi another hour down 100 atk runs brings it back to around 130

    No push

    email check hourly
    no wifi ni BT
    No Gps

    moderate use

    Could be why some are having battery issues

    this problem also exists before Rooting

    Hopefully 2.2 will remedy this issue

    As for rooting no real performance boost after bloatware removed
     

    Advertisement

  2. Martimus

    Martimus One bite at a time...
    843

    Jul 9, 2010
    19,535
    4,045
    843
    Male
    Engineer
    'neath a cactus
    Given that Android, by definition, starts and stops processes as needed, are you certain that it's a memory leak and not just Android allocating memory for a process that needs it?
     
  3. Helicrewchief

    Helicrewchief Well-Known Member
    43

    Jun 30, 2010
    191
    31
    43
    Blackhawk Crewchief
    North Carolina
    Is the Android OS capable of memory leaks? It prioritizes everything and if it needs the memory it just force closes the lowest priority correct?
     
  4. CarControl

    CarControl Member
    15

    Nov 25, 2009
    14
    0
    15
    Well, by definition a memory leak is a piece of memory not being referenced by a pointer, so the only way to get rid of a memory leak would be to clear all of the memory (reboot). And really all it takes is a bad programmer to create memory leaks.
     
  5. _Aardvark

    _Aardvark Well-Known Member
    53

    Jun 24, 2010
    376
    76
    53
    NJ
    Sorry, I feed the need to nickpick:

    1. A memory leak is not just memory (*allocated* memory you mean) not referenced by a pointer (not that isn't a great way to leak). At the most basic level a 'memory leak' is memory that should have been free, but wasn't.

    2. In most operating systems memory is tracked per-process (instance of a running program.) Closing that application would free all memory that program allocated, leaked or not. (having allocated memory at program shutdown, however, is often a sign of leaks) So rebooting is not the only way to free the memory, you should just be able to close the offending application.

    3. I've known many excellent programmers who were responsible for memory leaks.
     
  6. quickaudi

    quickaudi Well-Known Member
    173

    Jul 15, 2010
    3,063
    408
    173
    TN
    Fyi, it is NITpick, not nickpick ;)
     
  7. xander66

    xander66 Well-Known Member
    16

    Jul 13, 2010
    63
    6
    16
    Lol now that's some nitpicking.
     
  8. dookie1

    dookie1 Well-Known Member
    36

    Jun 25, 2010
    236
    9
    36
    as i said in another thread, memory is there to be used. running apps *should* consume it as is necessary for optimal performance. they should also release it when called for. the fact that your memory decrease over time (& use) should not be surprising. 'leak' is a misleading term. ATK is doing you no good. i mean, why is idle memory a desirable goal?

    that said, if you are experiencing performance issues that you can reliably attribute to low memory...well, that is certainly a problem. i just think that trying to maximize your idle memory is ridiculous.
     
  9. colchiro

    colchiro Well-Known Member
    323

    Jun 4, 2010
    8,886
    1,784
    323
    Male
    Web developer/IT

Share This Page

Loading...