Status: Available Owner: [email protected] Labels: Type-Cleanup Pri-3 OS-Windows Area-BrowserBackend Performance HelpWanted
New issue 6830 by [email protected]: Use native file locking semantic for logging http://code.google.com/p/chromium/issues/detail?id=6830 In LogMessage::~LogMessage(), the mutex log_mutex is used to coordinate multi-process writing to a file. This is overkill. LockFileEx() / UnlockFile() should be used instead. This way, in logging.cc, log_mutex could be removed and DCHECK(r != WAIT_ABANDONED); could never be hit again. This DCHECK is flaky, hides the original message and causes recursion in the logging system. -- 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 -~----------~----~----~----~------~----~------~--~---
