Comment #19 on issue 28547 by [email protected]: Chrome causing -10810 errors? http://code.google.com/p/chromium/issues/detail?id=28547
Testers: Here are the steps to verify. This needs to be done on Leopard and especially Snow Leopard. 1. Install Google Chrome 2. From the commandline, run: "launchctl bslist | wc l" and note the number. 3. Start Google Chrome on a fresh profile. 4. Once a browser window has opened, do #2 again, and note the number it should have increased (by 2). 5. Close the tab, and do #2 again. The number should have decreased by 1. 6. Open tabs, navigate, etc., and do #2 between each stage. Whenever a new (e.g., renderer) process is started, the number should increase (e.g., when you go to a "new" site). When a process is terminated (e.g., you close the last tab for a particular site), the number should decrease. 7. Quit, and do #2 again. Hopefully, the number should be the same as the first time. Compare what you see with the current beta channel. On the current beta channel, the number you see won't decrease on a renderer quit (unless it crashes, in which case Breakpad takes care of it). Try also, as John Grabowski suggests, getting renderers, plugins, etc. to crash. Please try to make sure that we don't leave hung renderers around under any reasonable circumstance. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
