Status: Untriaged Owner: [email protected] Labels: Type-Bug Pri-2 OS-Windows Area-BrowserBackend Size-Medium
New issue 9593 by [email protected]: ProcessSingleton race condition http://code.google.com/p/chromium/issues/detail?id=9593 What steps will reproduce the problem? Open chrome browsers rapidly, it is most reproducible if chrome has just been upgraded. What is the expected output? What do you see instead? Expected: the second browser process finds the first and forwards the command line which cause a new tab to open on the first browser. Second browser exits. Seen: the second browser does not detect the first and tries to open the profile db. It fails because it is locked by the first browser process. A disembodied error dialog (from chrome, not a crash) appears that has incomplete information. It is a race condition, but Anantha has a test that can make it happen 10 to 20% of the time. Cause: The ProcessSingleton does a look + acquire not close in time, if there is an upgrade there can be seconds between the two operations. I have no clue why even the look (during ctor) and the acquire (called Create()) are distinct methods, I think this should be done automatically at construction. -- 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 -~----------~----~----~----~------~----~------~--~---
