Comment #17 on issue 28547 by [email protected]: Chrome causing -10810 errors? http://code.google.com/p/chromium/issues/detail?id=28547
So, AFAICT, what's happening is that the fast-track way of ending a renderer is to just send it a SIGTERM, which we don't handle. Here's a patch which installs a handler which should clean it up: http://codereview.chromium.org/484007 (Not yet tested, as I don't have a branded build, and I have a bus to catch in 5 minutes....) I'm not the expert on this stuff though. (Is there other stuff we might want to clean up? Other signals we want to handle? Is calling DestructCrashReporter() from there safe?) Mark? -- 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
