You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
app.requestSingleInstanceLock on Windows currently (Electron 18.2.3) uses a named pipe to send data (called an acknowledgement) from the first instance back to the second instance. A potential issue with named pipes is that multiple "second instances" might open at the same time, in which case the acknowledgement might not get sent back to the correct second instance in the case that the named pipe name doesn't distinguish between which instance connected. I still have to read up on #34139 and understand how exactly the pipe name is being created, though.
By using message windows, I'm thinking that we can also start up the second instance's message window ahead of time, so that the first instance can directly send back a message, without having to first go through a handshake.
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment!
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue on a supported version of Electron please open a new issue and include instructions for reproducing the issue.
app.requestSingleInstanceLock
on Windows currently (Electron 18.2.3) uses a named pipe to send data (called an acknowledgement) from the first instance back to the second instance. A potential issue with named pipes is that multiple "second instances" might open at the same time, in which case the acknowledgement might not get sent back to the correct second instance in the case that the named pipe name doesn't distinguish between which instance connected. I still have to read up on #34139 and understand how exactly the pipe name is being created, though.By using message windows, I'm thinking that we can also start up the second instance's message window ahead of time, so that the first instance can directly send back a message, without having to first go through a handshake.
CC @deepak1556
The text was updated successfully, but these errors were encountered: