So... Im not 100% sure this is real or not... but here is my story
I noticed months ago that sometimes, my alarm clock just doesnt go off (in fact, it did it this morning... almost slept through work) and after some searching in the forums, came to the conclusion that it was my task killer that was causing this problem. anytime i "killed all apps" it would kill the clock and the alarm would not go off.
now, jump forward to the release of 2.1.3 leak. I install it, and as I have been doing since i realized this problem, dont include the clock app in the "kill all" of the task killer. However, i started noticing that at the end of the day, my available memory with all apps killed, not including the clock app, was getting smaller and smaller. so last night i waited until the available free memory with only the clock app running was ~40mb (which is RIDICULOUSLY LOW for the eris, i dont know why its so low, i dont have THAT many apps) i opened the task killer and with only the tk and the clock app running, i killed the clock app... all of a sudden... 20 mb are added to my free memory... 20 MB!!!! can the clock app really be using that much memory!?!?! i tested this morning... after killing the clock, opening it, setting an alarm, going back to home, going to TK, killing clock, only freed up about 4-5mb...
so... im concluding that it was the fact that i left my clock open all day that caused that massive 20mb freeing when the clock app was killed... which is 5x larger than the memory freed by the clock when its killed minutes after opening..
anyone else seeing anything like this? it was noticeably slowing down my phone, and it really seems to me at least that the clock app isnt managing memory too well.
if i am the only one let me know, maybe its something on my device only that i need to fix.
I noticed months ago that sometimes, my alarm clock just doesnt go off (in fact, it did it this morning... almost slept through work) and after some searching in the forums, came to the conclusion that it was my task killer that was causing this problem. anytime i "killed all apps" it would kill the clock and the alarm would not go off.
now, jump forward to the release of 2.1.3 leak. I install it, and as I have been doing since i realized this problem, dont include the clock app in the "kill all" of the task killer. However, i started noticing that at the end of the day, my available memory with all apps killed, not including the clock app, was getting smaller and smaller. so last night i waited until the available free memory with only the clock app running was ~40mb (which is RIDICULOUSLY LOW for the eris, i dont know why its so low, i dont have THAT many apps) i opened the task killer and with only the tk and the clock app running, i killed the clock app... all of a sudden... 20 mb are added to my free memory... 20 MB!!!! can the clock app really be using that much memory!?!?! i tested this morning... after killing the clock, opening it, setting an alarm, going back to home, going to TK, killing clock, only freed up about 4-5mb...
so... im concluding that it was the fact that i left my clock open all day that caused that massive 20mb freeing when the clock app was killed... which is 5x larger than the memory freed by the clock when its killed minutes after opening..
anyone else seeing anything like this? it was noticeably slowing down my phone, and it really seems to me at least that the clock app isnt managing memory too well.
if i am the only one let me know, maybe its something on my device only that i need to fix.
