-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Comments
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 ?
|
Somebody reported the same issue in Discord:
Note to myselfIt'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. |
Hi Antoine. I’m the admin running win 10. It has worked fine when I’ve
logged in the last two days. The computer itself is relatively powerful but
is 11 years old now and does struggle a bit with number of apps trying to
load on booting up. Maybe that’s the issue? Just a resources conflict?
On Fri, 5 Jun 2020 at 4:51 am, Antoine Aflalo ***@***.***> wrote:
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
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#463 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AP2V46WLBEBLTETDWHNKCMTRU7ULBANCNFSM4NSM36BA>
.
--
Ian Woods
iwoods2807@gmail.com
ian.g.woods@det.nsw.gov.au
|
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
The text was updated successfully, but these errors were encountered: