This is the relevant part of the log, as far as I can tell:
06-05 18:02:21.531: INFO/ActivityManager(1282): Displayed activity
com.google.android.gm/.ComposeActivity: 2025 ms (total 2631 ms)
06-05 18:02:22.101: ERROR/cache(2780): disableTransaction is out of sync
06-05 18:02:22.242: INFO/ActivityManager(1282): Process com.android.browser
(pid 2780) has died.
06-05 18:02:22.242: INFO/ActivityManager(1282): Low Memory: No more
background processes.
06-05 18:02:22.242: INFO/WindowManager(1282): WIN DEATH: Window{4507b368
com.android.browser/com.android.browser.BrowserActivity paused=false}
06-05 18:02:25.187: WARN/KeyCharacterMap(4253): Can't open keycharmap file
06-05 18:02:25.187: WARN/KeyCharacterMap(4253): Error loading keycharmap
file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'.
hw.keyboards.65538.devname='qtouch-touchscreen'
06-05 18:02:25.187: WARN/KeyCharacterMap(4253): Using default keymap:
/system/usr/keychars/qwerty.kcm.bin
06-05 18:02:26.555: INFO/NotificationService(1282): enqueueToast pkg=
com.google.android.gmcallback=android.app.itransientnotification$stub$pr...@44de28d0duration=0
06-05 18:02:26.601: ERROR/Workspace(1364): mCurrentScreen = 1
06-05 18:02:26.633: WARN/InputManagerService(1282): Starting input on
non-focused client
com.android.internal.view.iinputmethodclient$stub$pr...@44e4edb0 (uid=10007
pid=4253)
06-05 18:02:26.633: WARN/IInputConnectionWrapper(4253): showStatusIcon on
inactive InputConnection
06-05 18:02:28.000: INFO/ActivityManager(1282): Starting activity: Intent {
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER]
flg=0x10200000 cmp=com.android.browser/.BrowserActivity
bnds=[125,446][235,564] }
06-05 18:02:28.055: INFO/ActivityManager(1282): Start proc
com.android.browser for activity com.android.browser/.BrowserActivity:
pid=4265 uid=10045 gids={3003, 1015}
06-05 18:02:28.109: INFO/dalvikvm(4265): Debugger thread not active,
ignoring DDM send (t=0x41504e4d l=38)
06-05 18:02:28.180: INFO/dalvikvm(4265): Debugger thread not active,
ignoring DDM send (t=0x41504e4d l=42)
06-05 18:02:28.289: INFO/ActivityThread(4265): Publishing provider browser:
com.android.browser.BrowserProvider
06-05 18:02:29.164: DEBUG/BrowserSettings(4265): Enter
getFactoryResetHomeUrl()
06-05 18:02:29.164: DEBUG/BrowserSettings(4265): http index is 14
06-05 18:02:29.164: DEBUG/BrowserSettings(4265): Preload homepage is
http://www.google.com
06-05 18:02:29.398: DEBUG/dalvikvm(4265): GC freed 1981 objects / 142280
bytes in 175ms
06-05 18:02:30.453: INFO/ActivityManager(1282): Displayed activity
com.android.browser/.BrowserActivity: 2410 ms (total 2410 ms)
It starts more or less at the launching of the Gmail app and ends at the
browser being relaunched after it was killed due to low memory.
On Sat, Jun 5, 2010 at 6:09 PM, Simon Broenner <[email protected]>wrote:
> I just went through the whole process and logged it:
>
> 1. Open browser
> 2. Open maximum number of windows by using "open in new window" (set to
> open new windows in background, in case that matters), all with different
> content (so not all the same link)
> 3. Switch to a different application (in my case I clicked an e-mail
> address from the browser, which launched the Gmail app)
> 4. Then switch back to the browser, either via a long hold on the Home key
> or from the Home Screen Launcher
>
> Log: http://www.narcotic-symphony.de/simon/androidlog.txt
>
> Relaunching the browser (Step 4) takes place at around line line 161.
>
> Can you make heads or tails of it?
>
>
> Thanks for your help so far!
>
>
> On Sat, Jun 5, 2010 at 5:51 PM, Mark Murphy <[email protected]>wrote:
>
>> Simon Broenner wrote:
>> > Hmmm, I'm beginning to get that feeling too.
>> >
>> > Any idea what the cause could be? Obviously I'm not using any auto task
>> > killers or anything like that... :(
>>
>> Off the top of my head, no.
>>
>> If you're a developer, and you can get it to happen, plug it into USB
>> and scan logcat for any interesting messages. Usually, Android logs when
>> it is killing off processes, and it feels like your Browser process is
>> getting killed.
>>
>> If you're not a developer, the only advice I can offer is for you to
>> come up with a repeatable scenario that consistently causes the problem,
>> preferably from a freshly-rebooted phone.
>>
>> (even more ideally would be a phone with no third-party apps, but I'm
>> guessing this is your personal phone, so having you wipe it would be a
>> bit intrusive)
>>
>> If you can find such a scenario, post it here or on [android-discuss],
>> so we can see if other devices exhibit the same behavior. If we can find
>> cases across several devices, it's probably an Android bug. If the only
>> other cases are Milestones, it might be a Motorola bug. If we can't
>> reproduce the problem, I'd start taking a real close look at any
>> third-party apps you have installed.
>>
>> --
>> Mark Murphy (a Commons Guy)
>> http://commonsware.com | http://github.com/commonsguy
>> http://commonsware.com/blog | http://twitter.com/commonsguy
>>
>> Android Training...At Your Office: http://commonsware.com/training
>>
>> --
>> 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]<android-developers%[email protected]>
>> For more options, visit this group at
>> http://groups.google.com/group/android-developers?hl=en
>>
>
>
>
> --
> Simon Broenner
>
--
Simon Broenner
--
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
