[chromium-bugs] Issue 17952 in chromium: Logic to detect if browser is already running is inaccurate

Comment #12 on issue 17952 by kzjeef: Logic to detect if browser is already running is inaccurate http://code.google.com/p/chromium/issues/detail?id=17952 Do we need some more "advantage" or "stable" mechanism to detect if browser is already running ? -- You received this message because yo

[chromium-bugs] Issue 17952 in chromium: Logic to detect if browser is already running is inaccurate

Comment #11 on issue 17952 by su...@chromium.org: Logic to detect if browser is already running is inaccurate http://code.google.com/p/chromium/issues/detail?id=17952 It's possible. I'll look into this issue and give you feedback asap. James Su -- You received this message because you are li

[chromium-bugs] Issue 17952 in chromium: Logic to detect if browser is already running is inaccurate

Updates: Cc: su...@chromium.org Comment #10 on issue 17952 by e...@chromium.org: Logic to detect if browser is already running is inaccurate http://code.google.com/p/chromium/issues/detail?id=17952 Conveniently, the SCIM author has an @chromium address! James: is it possible that my g

[chromium-bugs] Issue 17952 in chromium: Logic to detect if browser is already running is inaccurate

Updates: Labels: Mstone-LinuxBeta Comment #9 on issue 17952 by e...@chromium.org: Logic to detect if browser is already running is inaccurate http://code.google.com/p/chromium/issues/detail?id=17952 Haha awesome. So it's probably that somehow our IME stuff causes scim to fork() off