> > >> The default max procs per userid on 10.5.8 is 266. With ~20 Chromes and >> 10 tabs each you're starting to get real close. Perhaps that's the real >> problem? >> > > That's a fair reasoning but then it should have been so all along. And I > reach the same state even with 10 chrome instances, only it takes a few mins > longer. >
Perhaps other factors (e.g. pages load 1% faster) have pushed us over a threshold where this problem is noticed. Or perhaps tvl was right about plugins working better. Not sure it matters much given what you found below... However, setting ulimit -u 512 does make it better, and I don't run out of > resources, so there it is. > I'm still trumped as to how it was fine until 2 weeks ago. And does it mean > that bad things will happen for a user with 20+ tabs? > > No; bad things will happen for a user with 20+ tabs only if they run 10 copies of Chrome at once. Chrome has reasonable renderer process limits so you won't hit this limit with Chrome and 500 tabs. jrg -- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
