Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SoundSwitch crash at start: Named Pipe access denied #463

Closed
iwoods2807 opened this issue Jun 4, 2020 · 3 comments
Closed

SoundSwitch crash at start: Named Pipe access denied #463

iwoods2807 opened this issue Jun 4, 2020 · 3 comments
Labels
Bug Issues which are bug reports Bug-Crash Issues which are related to a crash Confirmed Confirmed issues

Comments

@iwoods2807
Copy link

Both previous crashes when the computer was simply booting up (app set to launch with boot).
I tried running the application again from within the Roaming folder but it crashed immediately (not sure why the crashlog wasn't created but was within a few minutes of the 4th June crashlog attached)
SoundSwitch-crashlog-4_6_2020.zip
SoundSwitch-crashlog-31_5_2020.zip

@iwoods2807 iwoods2807 added Bug Issues which are bug reports Bug-Crash Issues which are related to a crash labels Jun 4, 2020
@Belphemur Belphemur changed the title Crashlogs SoundSwitch crash at start: Named Pipe access denied Jun 4, 2020
@Belphemur
Copy link
Owner

The first crash of the 31st was fixed in the 5.3.0 version.

The second crash of 4th of June is actually a new one that I'll have to investigate.

Can you give me more information about your machine ?

  • How did you install SoundSwitch (as User or Admin) ?
  • What your version of Windows ?
    • WIN+R > sysver

@Belphemur
Copy link
Owner

Belphemur commented Jun 5, 2020

Somebody reported the same issue in Discord:

I'm getting crashes when logging in with two windows accounts at the same time, both running SoundSwitch. just thought you should know.

Note to myself

It's related to the new name piped system used to check if SoundSwitch is already running and tell the old instance to stop to let the new one start.

Problem: The right on the created named pipe is by user... I'll have to see what can be done with the Named Pipe and the Mutex to let 2 instances on different users run simultaneously.

Belphemur added a commit that referenced this issue Jun 6, 2020
@iwoods2807
Copy link
Author

iwoods2807 commented Jun 7, 2020 via email

@Belphemur Belphemur added the Confirmed Confirmed issues label Jun 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues which are bug reports Bug-Crash Issues which are related to a crash Confirmed Confirmed issues
Projects
None yet
Development

No branches or pull requests

2 participants