diff options
| author | eroman@chromium.org <eroman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-31 03:08:44 +0000 |
|---|---|---|
| committer | eroman@chromium.org <eroman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-03-31 03:08:44 +0000 |
| commit | 2984008f7136500a2831160f72846b94640b37ff (patch) | |
| tree | ee92610da0b816c419b79f44000ee6752aabb037 /chrome | |
| parent | 3f6d3a27d274d2f71a3c94e711698447f8a3993e (diff) | |
| download | chromium_src-2984008f7136500a2831160f72846b94640b37ff.zip chromium_src-2984008f7136500a2831160f72846b94640b37ff.tar.gz chromium_src-2984008f7136500a2831160f72846b94640b37ff.tar.bz2 | |
Revert 43127 [It resulted in a free memory write because of a consumer that was relying on the old ordering (BUG=39932).]
Don't call Thread::CleanUp() before the MessageLoop destruction observers have run.
This is consistent with the comment for Thread::CleanUp(), which says it runs after the message loop has "stopped".
Certain consumers depend on this ordering to avoid accessing variables which are deleted by Thread::CleanUp().
BUG=39723
TEST=ThreadTest.CleanUp
Review URL: http://codereview.chromium.org/1540002
TBR=eroman@chromium.org
Review URL: http://codereview.chromium.org/1517006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@43174 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome')
0 files changed, 0 insertions, 0 deletions