View Single Post
Posts: 114 | Thanked: 201 times | Joined on Apr 2009
#46
Originally Posted by qwerty12 View Post
~ $ pidof /usr/sbin/browserd
~ $ pidof browserd
2071 2051 1840 1797 1206
~ $

For reference:
1206 user 37712 S /usr/sbin/browserd -d
1797 user 39960 S /usr/sbin/browserd -d -b
1840 user 65372 S /usr/sbin/browserd -s 1840 -n RTComMessagingServer
2046 user 3336 S /usr/bin/browser-switchboard
2051 user 39964 S /usr/sbin/browserd -d -b
2052 user 3936 S browser
2053 user 29368 S browser
2071 user 55408 S /usr/sbin/browserd -s 2071 -n browserui
2149 user 2092 S grep browser

[No MicroB windows are visible on my screen; tho, I guess that some browserd's can be attributed to the preloading of the Conversations app which also uses a browserd for its interface]
Oookay, so now we have three browserd -d master processes -- it seems to be launching one for each time you start MicroB using Browser Switchboard. That's just odd -- "pidof /usr/sbin/browserd" doesn't return a nonzero exit code, by any chance?

EDIT: Okay, I see why that's happening, never mind -- we should be doing just "pidof browserd".

Even more strangely, we now have "browser" processes -- I'm guessing if you change the default browser back to something other than MicroB, links still open in MicroB? Do those browser processes quit if you run
Code:
dbus-send --session --type=method_call --print-reply --dest="com.nokia.osso_browser" /com/nokia/osso_browser/request com.nokia.osso_browser.exit_browser
? Any chance you can reproduce this (having browser processes open after launching MicroB with Browser Switchboard and then closing the browser windows) starting from a freshly booted device, and provide the debug output coming from browser-switchboard along the way?
 

The Following 3 Users Say Thank You to steven676 For This Useful Post: