Comment #6 on issue 29240 by [email protected]: Should not use dynamic
memory in signal handlers
http://code.google.com/p/chromium/issues/detail?id=29240
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=34036
------------------------------------------------------------------------
r34036 | [email protected] | 2009-12-07 20:22:50 -0800 (Mon, 07 Dec
2009) | 6 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/logging.cc?r1=34036&r2=34035
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/logging.h?r1=34036&r2=34035
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/browser_main.cc?r1=34036&r2=34035
Make POSIX SIGTERM/SIGINT/SIGHUP handler async signal safe.
* Don't use LOG/CHECK. Replace with RAW_LOG/DCHECK (newly added to
logging.h)
* Don't directly post a task to the UI loop. Write to a magic pipe. Read
this from a separate thread which will post to a task to the UI loop.
BUG=http://crbug.com/29240
Review URL: http://codereview.chromium.org/460094
------------------------------------------------------------------------
--
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
