0.13.0 rc4 able to launch once from desktop shortcut, cannot launch again after quitting

[alexwykoff]

• Did you search for similar issues before submitting this one?
  yes

• Describe the issue you encountered:
  after launching brave and quitting, i cannot launch brave again

• Platform (Win7, 8, 10? macOS? Linux distro?):
  tested on win10 x64

• Brave Version (revision SHA):
  0.13.0 rc4 (40dffe8)

• Steps to reproduce:

  1. start (or restart) a vm
  2. launch brave from the desktop shortcut
  3. quit brave
  4. try to launch brave again from the desktop shortcut

• Actual result:
  two processes start then quit

• Expected result:
  brave should launch

• Will the steps above reproduce in a fresh profile? If not what other info can be added?
  yes

• Is this an issue in the currently released version?
  no

• Can this issue be consistently reproduced?
  yes

• Extra QA steps:
  1.
  2.
  3.

• Screenshot if needed:

2017-01-20 18-30-17.mp4.zip

• Any related issues:

[alexwykoff]

6793_roaming.zip

[alexwykoff]

BraveProcmonLogfile.zip

[alexwykoff]

[3580:3092:0120/171316:VERBOSE1:crash_service_main.cc(77)] Session start. cmdline is [--reporter-url=https://brave-laptop-updates.herokuapp.com/1/crashes "--application-name=Brave Developers" --v=1] [3580:3092:0120/171316:VERBOSE1:crash_service.cc(142)] window handle is 0000000000010360 [3580:3092:0120/171316:VERBOSE1:crash_service.cc(284)] pipe name is \\.\pipe\Brave Developers Crash Service dumps at C:\Users\test\AppData\Local\Temp\Brave Developers Crashes [3580:3092:0120/171316:VERBOSE1:crash_service.cc(288)] checkpoint is C:\Users\test\AppData\Local\Temp\Brave Developers Crashes\crash_checkpoint.txt server is https://brave-laptop-updates.herokuapp.com/1/crashes maximum 128 reports/day reporter is Brave-crash-service [3580:3092:0120/171316:VERBOSE1:crash_service_main.cc(94)] Ready to process crash requests [3580:2480:0120/171316:VERBOSE1:crash_service.cc(317)] client start. pid = 3800 [3580:4688:0120/171336:VERBOSE1:crash_service.cc(325)] client end. pid = 3800 [3580:4688:0120/171337:VERBOSE1:crash_service.cc(346)] zero clients. exiting [3580:3092:0120/171337:VERBOSE1:crash_service.cc(486)] session ending.. [3580:3092:0120/171337:VERBOSE1:crash_service.cc(491)] clients connected :1 clients terminated :1 dumps serviced :0 dumps reported :0 [3580:3092:0120/171337:VERBOSE1:crash_service_main.cc(99)] Session end. return code is 0 [5908:5912:0120/171856:VERBOSE1:crash_service_main.cc(77)] Session start. cmdline is [--reporter-url=https://brave-laptop-updates.herokuapp.com/1/crashes "--application-name=Brave Developers" --v=1] [5908:5912:0120/171856:VERBOSE1:crash_service.cc(142)] window handle is 00000000001C01BE [5908:5912:0120/171856:VERBOSE1:crash_service.cc(284)] pipe name is \\.\pipe\Brave Developers Crash Service dumps at C:\Users\test\AppData\Local\Temp\Brave Developers Crashes [5908:5912:0120/171856:VERBOSE1:crash_service.cc(288)] checkpoint is C:\Users\test\AppData\Local\Temp\Brave Developers Crashes\crash_checkpoint.txt server is https://brave-laptop-updates.herokuapp.com/1/crashes maximum 128 reports/day reporter is Brave-crash-service [5908:5912:0120/171856:VERBOSE1:crash_service_main.cc(94)] Ready to process crash requests [5908:3580:0120/171856:VERBOSE1:crash_service.cc(317)] client start. pid = 5748 [5908:4544:0120/171903:VERBOSE1:crash_service.cc(325)] client end. pid = 5748 [5908:4544:0120/171904:VERBOSE1:crash_service.cc(346)] zero clients. exiting [5908:5912:0120/171904:VERBOSE1:crash_service.cc(486)] session ending.. [5908:5912:0120/171904:VERBOSE1:crash_service.cc(491)] clients connected :1 clients terminated :1 dumps serviced :0 dumps reported :0 [5908:5912:0120/171904:VERBOSE1:crash_service_main.cc(99)] Session end. return code is 0
from operation_log

coincides with
Logfile.zip 5:19

[bsclifton]

related?
#5577

[bbondy]

@aekeus @alexwykoff could you see @bsclifton 's question above?

[aekeus]

Seems quite likely. Hopefully we can reach out to @Legitgamer264 for confirmation.