Comment #3 on issue 30960 by [email protected]: Tsan race in NetworkChangeNotifierMac http://code.google.com/p/chromium/issues/detail?id=30960
Ah, yes - it looks like it is safe to override CleanUp() if you call Stop() explicitly in the constructor. We report a possible data race because the compiler generates a code which re-writes the vfptr on each destructor entry. As a result, the vfptr is re-written when entering ~NetworkChangeNotifierThread() with the same value as it is already containing. We don't distinguish the values written to racing memory in TSan. Maybe we should try doing it at least for vfptr's. -- 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
