UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.33 Safari/537.36

Steps to reproduce the problem:
1. chromium is not running
2. User does e.g.,
$ chromium https://www.google.com/search?q=A & chromium https://www.google.com/search?q=B
thinking he will end up with what would have been better invoked as
$ chromium https://www.google.com/search?q=A https://www.google.com/search?q=B
3. Computer enters race condition which locks up entire computer,
forcing user to have to power cycle the computer, recovering disk
journals etc.

What is the expected behavior?

What went wrong?
Yes, with just a few seconds
$ chromium & sleep 3; chromium
chromium's built in race control mechanisms mean that it will simply
open a new tab in an existing session.

See mkstemp, mkostemp, mkstemps, mkostemps - create a unique temporary file
for examples of avoiding race conditions.

You need to eliminate the race condition altogether from second 0.

Crashed report ID: 

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 68.0.3440.33  Channel: n/a
OS Version: 
Flash Version: