It showed the GREF count going all over the place. It would increase as the
activity paused and resumed. It would go from 99 to 201 to 301 alll the way
up to 801 or higher sometimes. The more I paused it (just by going to a
different app) and returned (using the back button) the higher it went. I
can't figure it out for the life of me. If i continued to do it, my app
would crash.
Also, sometimes the GREF count would come back down, seemingly randomly, in
between pauses and resumes... but it would inevitably increase way too much.
Here's a trace (sorry for the length):
.
.
.
D/dalvikvm( 198): GREF has increased to 201
W/KeyCharacterMap( 93): No keyboard for id 0
W/KeyCharacterMap( 93): Using default keymap:
/system/usr/keychars/qwerty.kcm.bin
D/dalvikvm( 93): GREF has increased to 301
D/dalvikvm( 93): GC freed 1636 objects / 77552 bytes in 112ms
D/dalvikvm( 50): GREF has increased to 301
D/dalvikvm( 198): GC freed 2565 objects / 136904 bytes in 166ms
D/dalvikvm( 93): GREF has increased to 401
D/dalvikvm( 50): GC freed 5157 objects / 299552 bytes in 219ms
D/dalvikvm( 198): GREF has increased to 301
D/dalvikvm( 93): GREF has increased to 501
D/dalvikvm( 93): GC freed 1231 objects / 57712 bytes in 134ms
I/ActivityManager( 50): Starting activity: Intent {
action=android.intent.action.DIAL
comp={com.android.contacts/com.android.contacts.DialtactsActivity} }
W/ActivityManager( 50): Activity is launching as a new task, so cancelling
activity result.
D/dalvikvm( 93): GREF has decreased to 399
D/dalvikvm( 93): GC freed 2222 objects / 104288 bytes in 127ms
D/dalvikvm( 93): GREF has decreased to 299
I/ActivityManager( 50): Displayed activity
com.android.contacts/.DialtactsActivity: 2009 ms
W/KeyCharacterMap( 93): No keyboard for id 0
W/KeyCharacterMap( 93): Using default keymap:
/system/usr/keychars/qwerty.kcm.bin
D/dalvikvm( 93): GREF has increased to 401
D/dalvikvm( 93): GC freed 994 objects / 31992 bytes in 109ms
D/dalvikvm( 198): GC freed 1692 objects / 116888 bytes in 117ms
D/dalvikvm( 93): GREF has increased to 501
D/dalvikvm( 50): GC freed 3214 objects / 149176 bytes in 152ms
D/dalvikvm( 93): GC freed 703 objects / 28328 bytes in 114ms
D/dalvikvm( 93): GREF has increased to 601
D/dalvikvm( 198): GREF has increased to 401
D/dalvikvm( 50): GREF has increased to 401
I/ActivityManager( 50): Starting activity: Intent {
action=android.intent.action.DIAL
comp={com.android.contacts/com.android.contacts.DialtactsActivity} }
W/ActivityManager( 50): Activity is launching as a new task, so cancelling
activity result.
D/dalvikvm( 198): GC freed 9794 objects / 506928 bytes in 168ms
D/dalvikvm( 93): GREF has decreased to 499
D/dalvikvm( 50): GREF has decreased to 299
D/dalvikvm( 93): GC freed 3207 objects / 149160 bytes in 107ms
D/dalvikvm( 198): GREF has decreased to 299
I/ActivityManager( 50): Displayed activity
com.android.contacts/.DialtactsActivity: 3236 m
D/dalvikvm( 93): GREF has decreased to 399
W/KeyCharacterMap( 93): No keyboard for id 0
W/KeyCharacterMap( 93): Using default keymap:
/system/usr/keychars/qwerty.kcm.bin
D/dalvikvm( 93): GREF has increased to 501
D/dalvikvm( 93): GC freed 1852 objects / 74648 bytes in 127ms
D/dalvikvm( 50): GC freed 2191 objects / 86456 bytes in 172ms
D/dalvikvm( 198): GREF has increased to 401
D/dalvikvm( 198): GC freed 2173 objects / 108880 bytes in 254ms
D/dalvikvm( 93): GREF has increased to 601
D/dalvikvm( 93): GC freed 523 objects / 16696 bytes in 118ms
D/dalvikvm( 50): GREF has increased to 401
D/dalvikvm( 93): GREF has increased to 701
D/dalvikvm( 198): GREF has increased to 501
D/dalvikvm( 93): GREF has increased to 801
D/dalvikvm( 93): GC freed 667 objects / 23816 bytes in 114ms
D/dalvikvm( 50): GC freed 1291 objects / 53032 bytes in 198ms
D/dalvikvm( 93): GREF has increased to 901
D/dalvikvm( 50): GREF has increased to 501
.
.
.
As you can see, 901 is not good. I don't know what could be causing a leak.
I'm keeping track of every variable as far as I know. This is so confusing.
On Mon, Jan 12, 2009 at 7:57 PM, fadden <[email protected]> wrote:
>
> On Jan 12, 12:43 pm, somecs <[email protected]> wrote:
> > This issue inevitably ends up crashing my program if I cause the
> > update process to run more than 3 or 4 times in a row (which is
> > definitely a possibility with normal use by the unsuspecting user), so
> > it is unacceptable. Of course, it's unacceptable no matter what, but
> > in any case, I am desperate to fix this. Can anyone help?
>
> What does "logcat" show? There should be a GREF summary message in
> the output.
>
> The cap should be at 2000 now, so overflowing is likely a leak.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
