| commit | 1446d8a685cfd4881985397cceacc761e891770f | [log] [tgz] |
|---|---|---|
| author | dmichael@chromium.org <dmichael@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | Thu Apr 17 14:07:18 2014 +0900 |
| committer | Qijiang Fan <fqj@google.com> | Thu Jun 04 16:29:35 2020 +0900 |
| tree | b5fc12114c39c5b7d00c1806b298b4b4afd5efeb | |
| parent | 038574855635bd81a4d10afeb0139b5743565b57 [diff] |
DCHECK that listener thread != IO thread This came up in code review, where somebody was creating a SyncChannel on the IO thread. That will easily lead to deadlocks. For ChannelProxy, it seems OK to have them be the same thread so long as there is no Listener. We apparently already do this in one place: https://code.google.com/p/chromium/codesearch#chromium/src/components/nacl/browser/nacl_process_host.cc&l=866 BUG= Review URL: https://codereview.chromium.org/234253002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@264424 0039d316-1c4b-4281-b951-d872f2087c98 CrOS-Libchrome-Original-Commit: 1f9cf47eb30c2974daad65c7e4a2415efb01a43d