diff options
author | posciak@chromium.org <posciak@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-04-25 00:42:27 +0000 |
---|---|---|
committer | posciak@chromium.org <posciak@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-04-25 00:42:27 +0000 |
commit | 8c81e9eccca97e2de13c8a5fe3059f238492a066 (patch) | |
tree | fdfeaae2121b046e0b73f4a81396516c69df70a5 /base/files/file_path_watcher_stub.cc | |
parent | 6b2c67004e8e000ac7f9e0d2c2d9a437fa2c93b8 (diff) | |
download | chromium_src-8c81e9eccca97e2de13c8a5fe3059f238492a066.zip chromium_src-8c81e9eccca97e2de13c8a5fe3059f238492a066.tar.gz chromium_src-8c81e9eccca97e2de13c8a5fe3059f238492a066.tar.bz2 |
Fix sending log messages from GPU child threads
This fixes a problem with sending log messages from children threads of the GPU
process. In GPU process the message goes through GpuProcessLogMessageHandler()
and to ChildThread::Send(), but there it would fail on
DCHECK(MessageLoop::current() == message_loop()), try to output another
log message about it, and since the handler is overriden, it would go back to
GpuProcessLogMessageHandler, and back again to ChildThread::Send() and thus
recurse until eventually dying silently due to stack overflow.
BUG=
TEST=manual run of a GPU child thread
Review URL: http://codereview.chromium.org/9812022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@133824 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/files/file_path_watcher_stub.cc')
0 files changed, 0 insertions, 0 deletions