Is this thought to be http://crbug.com/29240, or are there other problems with the signal handler? The change to fix that is out at http://codereview.chromium.org/460094.
Mark Evan Stade wrote: > On Mon, Dec 7, 2009 at 1:41 PM, Paweł Hajdan Jr. <phajdan...@chromium.org> > wrote: >> >> On Mon, Dec 7, 2009 at 22:34, Glenn Wilson <gwil...@chromium.org> wrote: >> > Evan >> > >> > Triaging Linux Jank bugs. Probably not many that are actionable right >> > now, though. >> That's not exactly Jank issue, but on a lot of our bots we're getting >> leftover processes on Linux. It seems they don't respond properly to >> SIGTERM. This seems to have started after we added the handler for SIGTERM >> (previously chrome was using the default handler). So this causes quite a >> lot of flakiness, but is also kind-of janky. > > As you pointed out, this is not jank (i.e., sluggish user experience). Have > you filed a bug and cc'ed agl + willchan + mark (who I believe have worked > on the new handler)? > >> >> -- >> Chromium Developers mailing list: chromium-dev@googlegroups.com >> View archives, change email options, or unsubscribe: >> http://groups.google.com/group/chromium-dev > > -- > Chromium Developers mailing list: chromium-dev@googlegroups.com > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
