Skip to content
This repository has been archived by the owner. It is now read-only.

Profile in use by another Chromium process -- ERROR:process_singleton_posix.cc(323) #11829

Closed
aumars opened this Issue Nov 7, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@aumars
Copy link

commented Nov 7, 2017

Description

Brave fails to initialise at all.

Steps to Reproduce

  1. Install Brave using official instructions in Fedora
  2. Execute Brave in the terminal

Actual result:

Error: unrecognized flag --icu_case_mapping
Try --help for options
[7410:7410:1107/212703.629045:ERROR:process_singleton_posix.cc(323)] The profile appears to be in use by another Chromium process (2727) on another computer (localhost.localdomain). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium.

Reproduces how often:
It just spontaneously happened today for no apparent reason. I tried restarting the computer and reinstalling Brave but nothing seems to work.

Brave Version

about:brave info:
0.19.80-1

Reproducible on current live release:
Yes.

Additional Information

@bsclifton

This comment has been minimized.

Copy link
Member

commented Nov 30, 2017

@insanerwayner

This comment has been minimized.

Copy link

commented Feb 17, 2018

This happened to me today. On Pop_OS!.

May be related to me changin my hostname on my machine. Will try reverting and update with results.

@insanerwayner

This comment has been minimized.

Copy link

commented Feb 17, 2018

That didn't work either.

@insanerwayner

This comment has been minimized.

Copy link

commented Feb 17, 2018

Actually it did. I misspelled the first time. Set it back to the name of the computer it was showing in the error string and it worked. Now the question is. How can I avoid this after changing my hostname?

@amorrisbpsd

This comment has been minimized.

Copy link

commented Feb 28, 2018

I was able to fix this by removing the SingletonLock file.

rm /home/$USER/.config/brave/SingletonLock

@bsclifton bsclifton added the stale label Aug 6, 2018

@bsclifton bsclifton removed this from the Triage Backlog milestone Aug 6, 2018

@bsclifton

This comment has been minimized.

Copy link
Member

commented Aug 6, 2018

This usually happens when multiple instances of Brave are running (ex: if one got hung and is still running and then you open another). Closing since there haven't been any updates

@bsclifton bsclifton closed this Aug 6, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.