- Electron version: 0.37.7
- Operating system: MacOS 10.11.4

Create a directory with the attached `package.json` and `main.js` files. The app just calls `app.makeSingleInstance` (code sample copied from the Electron docs) and then creates an empty window.

[package.json.txt](https://github.com/electron/electron/files/233556/package.json.txt)
[main.js.txt](https://github.com/electron/electron/files/233558/main.js.txt)

Type:

```
    rm -rf ~/Library/Application\ Support/Electron
    npm start
```

The app will display

```
    ### version 0.37.7
    ### shouldQuit:  true
```

...even though no other instance is running.

If you create an empty ~/Library/Application\ Support/Electron directory, the app runs as expected.

(Obviously, any established Electron developer will have such a directory and will not notice this bug. Their users will notice it very quickly indeed.)

chromium_src/chrome/browser/process_singleton_posix.cc
std::string hostname;
  int pid;
  ParseLockPath(lock_path_, &hostname, &pid);
  if (!hostname.empty() && hostname != net::GetHostName()) {
    return DisplayProfileInUseError(lock_path_, hostname, pid);
  }
  UnlinkPath(lock_path_);
  if (IsSameChromeInstance(pid))
    return true;
  if (pid > 0) {
    kill_callback_.Run(pid);
    return true;
  }
  LOG(ERROR) << "Failed to extract pid from path: " << lock_path_.value();
  return true;
}
void ProcessSingleton::KillProcess(int pid) {
  
  int rv = kill(static_cast<base::ProcessHandle>(pid), SIGKILL);
  
  
  DCHECK(rv == 0 || errno == ESRCH) << "Error killing process: "
                                    << base::safe_strerror(errno);
}