Chromium only allows one process globally per user data directory, since two Chrome instances reading/writing to the same user profile directory is not going to go well. It's unclear to me if you want another instance of Chrome with a different command line (in which case, just use a --user-data-dir=<some path> to create a new instance, and use the new flag value), or if you'd rather close the existing session, in which case you can use whatever your platform's kill command is to kill chrome processes (Though that obviously won't cause Chromium to shut down cleanly - if you need to do that, I assume it would be more involved).