Comment #3 on issue 23551 by [email protected]: Chrome responds to a
SIGTERM as though it were a SIGKILL
http://code.google.com/p/chromium/issues/detail?id=23551
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=28225
------------------------------------------------------------------------
r28225 | [email protected] | 2009-10-06 20:09:33 -0700 (Tue, 06 Oct 2009)
| 8 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/browser_main.cc?r1=28225&r2=28224
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/browser_uitest.cc?r1=28225&r2=28224
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/ui/ui_test.cc?r1=28225&r2=28224
Adding a SIGTERM handler for OS_POSIX builds. This is needed so that
Chrome can shut down gracefully when many posix-based system halt or reboot
while Chrome is open.
SIGTERM may come in on any thread, so the handler creates a Task object
that wraps up a call to BrowserList::CloseAllBrowsers(true) and Posts it to
the message loop of the UI thread. Thus, we both get out of the signal
handler quickly and can deal with the signal on any thread.
BUG=23551
TEST=covered by BrowserTest.PosixSessionEnd
Review URL: http://codereview.chromium.org/255036
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
