Issue 73035 in chromium: Failed to create ProcessSingleton

409 views
Skip to first unread message

chro...@googlecode.com

unread,
Feb 15, 2011, 2:30:04 PM2/15/11
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined

New issue 73035 by john.pia...@gmail.com: Failed to create ProcessSingleton
http://code.google.com/p/chromium/issues/detail?id=73035

Chrome Version : 9.0.597.94 (Developer Build 0)

What steps will reproduce the problem?
1. try to run chromium

What is the expected result?
Chromium starts

What happens instead?
[5489:5489:484977335:ERROR:chrome/browser/process_singleton_linux.cc(949)]
Failed to create socket directory.
[5489:5489:484981651:ERROR:chrome/browser/browser_main.cc(1293)] Failed to
create a ProcessSingleton for your profile directory. This means that
running multiple instances would start multiple browser processes rather
than opening a new window in the existing process. Aborting now to avoid
profile corruption.

chro...@googlecode.com

unread,
Sep 6, 2012, 12:28:16 PM9/6/12
to chromi...@chromium.org

Comment #3 on issue 73035 by san...@gmail.com: Failed to create
ProcessSingleton
http://code.google.com/p/chromium/issues/detail?id=73035

After having upgraded to new version of google chrome under Kubuntu 12.04,
I now have the same issue:

$ ~/.config$ google-chrome
[4335:4335:4797865555:ERROR:process_singleton_linux.cc(907)] Failed to
create socket directory.
[4335:4335:4797866281:ERROR:chrome_browser_main.cc(1552)] Failed to create
a ProcessSingleton for your profile directory. This means that running
multiple instances would start multiple browser processes rather than
opening a new window in the existing process. Aborting now to avoid profile
corruption.


and deleting the /tmp directory doesn't help

chro...@googlecode.com

unread,
Sep 6, 2012, 12:44:17 PM9/6/12
to chromi...@chromium.org

Comment #4 on issue 73035 by san...@gmail.com: Failed to create
ProcessSingleton
http://code.google.com/p/chromium/issues/detail?id=73035

Sorry for the noise, the problem has disappeared after rebooting the
computer.

Reply all
Reply to author
Forward
0 new messages