On Wed, Dec 30, 2009 at 4:17 PM, Nirnimesh <nirnim...@chromium.org> wrote:
> +chromium-dev. This is mac only. > (resending from right id this time) > > Trung, Mark: I did see ps zombies, but they were from my long-standing > chrome, not from chromebot. I'm on 10.5.8. > Kris: I'm pretty sure chromebot worked fine on the 249 branch, at least > until 2 weeks ago. > TVL: Time Machine is off > and /Library/Preferences/com.apple.TimeMachine.plist is modest. I run > chromebot with each chrome instance running with its own profile dir. > Where are the profile dirs going on disk? Time machine doesn't have to be on, we can add things to this file incase it is turned on. > John: output of launchctl bslist over time attached. It goes from 196 to a > high of 244. Is this significant considering there are 20 instances of > chrome running? This number does however go down when chromebot kills some > chrome processes and then climbs back again when new instances are fired. > > I did notice one other interesting thing related to ps. As long as > chromebot runs, there were a number of "stuck" (though not zombies) ps > processes. Any additional ps commands in terminal gets stuck too. > > On Wed, Dec 30, 2009 at 10:37 AM, Viet-trung Luu <v...@google.com> wrote: > >> There may be several (possibly related) problems. >> >> I'm definitely seeing zombie ps-es on 249.43 (the released beta). What >> Nirnimesh said about not being able to fork processes (until Chrome >> gets killed) could be caused by zombies. >> >> Is anyone else seeing zombies? >> >> - Trung >> >> On Wed, Dec 30, 2009 at 1:28 PM, Thomas Van Lenten <thoma...@google.com> >> wrote: >> > >> > >> > On Wed, Dec 30, 2009 at 1:22 PM, Kris Rambish <kr...@google.com> wrote: >> >> >> >> A few questions: >> >> - Does this happen with the 249 (Beta) branch? >> >> - Do we know when this has gotten worse on TOT? >> >> + If we don't, does it make sense to fire up 15 minis with >> different >> >> builds and see where it breaks/gets worse? >> > >> > Look at /Library/Preferences/com.apple.TimeMachine.plist, how big is it? >> > When you run chromebot, what do you use for profile dirs? >> > TVL >> > >> >> >> >> Kris >> >> >> >> On Wed, Dec 30, 2009 at 12:33 AM, Viet-trung Luu <v...@google.com> >> wrote: >> >>> >> >>> We're (or at least I am) seeing ps zombies (which I thought had been >> >>> resolved). See >> >>> <http://code.google.com/p/chromium/issues/detail?id=28547#c29> >> >>> (I see it on 10.5.8 also). >> >>> >> >>> Anyone who has the cycles-- please feel free to investigate.... >> >>> >> >>> - Trung >> >>> >> >>> On Wed, Dec 30, 2009 at 3:08 AM, John Grabowski <j...@google.com> >> wrote: >> >>> > I agree; this sounds a lot like the Avi bug (worked around by trung >> on >> >>> > http://crbug.com/28547). >> >>> > Nirnimesh: you can test this by doing a "launchctl bslist | wc -l" >> and >> >>> > see >> >>> > if that number keeps rising to infinity (at which point the system >> >>> > chokes). >> >>> > jrg >> >>> > >> >>> > On Tue, Dec 29, 2009 at 9:01 PM, Thomas Van Lenten >> >>> > <thoma...@google.com> >> >>> > wrote: >> >>> >> >> >>> >> I think there is a fix/hack on trunk for the issue Avi had brought >> up. >> >>> >> Are they really stuck, or are they just really slow to respond? >> This >> >>> >> could >> >>> >> be the issue we are seeing with browser_tests and some of the perf >> >>> >> tests >> >>> >> where things are getting slower with time. >> >>> >> What really confuses me here, is the reference build doesn't show >> this >> >>> >> problem, and it's been updated to be a build from within the range >> >>> >> that >> >>> >> started showing this slowdown with time... >> >>> >> TVL >> >>> >> >> >>> >> >> >>> >> On Tue, Dec 29, 2009 at 11:52 PM, Nirnimesh <nirnim...@google.com> >> >>> >> wrote: >> >>> >>> >> >>> >>> Here is what happens when running chromebot on builds from the >> trunk >> >>> >>> for >> >>> >>> some time now: >> >>> >>> Chromebot fires off 20 instances of Chrome. It starts off fine but >> >>> >>> within >> >>> >>> a few minutes you cannot do anything on the machine and chrome too >> >>> >>> appears >> >>> >>> to be hung (until it gets killed by chromebot). Until then you >> cannot >> >>> >>> fork >> >>> >>> any processes, cannot launch any app, nothing. Is this similar to >> the >> >>> >>> other >> >>> >>> bug in beta about running out of resources (which avi brought up), >> or >> >>> >>> does >> >>> >>> this sound different? >> >>> >>> Thanks >> >>> >>> >> >>> >>> -- >> >>> >>> ../NiR >> >>> >> >> >>> > >> >>> > >> >> >> > >> > >> > > > > -- > ../NiR > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
