<blockquote>
<p>So first instance tries to bind - fails, fails creating one as well. But other instances do not try to bind ?</p>
</blockquote>
<p>Yes because they see the working mutex of the first instance and so try to connect to the TCP port instead of opening a new one. I added one more debug message for exact this case in <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/geany/geany/commit/ec10be0ddf6bc1a4f7c144de489cd553ccf7f161/hovercard" href="https://github.com/geany/geany/commit/ec10be0ddf6bc1a4f7c144de489cd553ccf7f161"><tt>ec10be0</tt></a>.<br>
The real problem remains in the failed bind of the first instance.</p>
<blockquote>
<p>Is 127.0.0.1:49876: 10013 changeable anywhere? Or is hard-coded</p>
</blockquote>
<p>It's hard-coded since it usually doesn't cause any problems. Even if, changing the port number probably won't solve your problem.</p>
<blockquote>
<p>Other lead is cygwin installation, maybe it has done some havoc. Are there any complains using stand-alone geany and cygwin?</p>
</blockquote>
<p>Not that I know of.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/2101#issuecomment-476869882">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ-DbzDcDGEClDacBi9Bb6_pYS8KHks5vaph9gaJpZM4blfy0">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJ6n_1elqkCJ7UT1oKYipod0LfKonks5vaph9gaJpZM4blfy0.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@eht16 in #2101: \u003e So first instance tries to bind - fails, fails creating one as well. But other instances do not try to bind ?\r\n\r\nYes because they see the working mutex of the first instance and so try to connect to the TCP port instead of opening a new one. I added one more debug message for exact this case in https://github.com/geany/geany/pull/2111/commits/ec10be0ddf6bc1a4f7c144de489cd553ccf7f161.\r\nThe real problem remains in the failed bind of the first instance.\r\n\r\n\u003e Is 127.0.0.1:49876: 10013 changeable anywhere? Or is hard-coded\r\n\r\nIt's hard-coded since it usually doesn't cause any problems. Even if, changing the port number probably won't solve your problem.\r\n\r\n\u003e Other lead is cygwin installation, maybe it has done some havoc. Are there any complains using stand-alone geany and cygwin? \r\n\r\nNot that I know of."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/2101#issuecomment-476869882"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/2101#issuecomment-476869882",
"url": "https://github.com/geany/geany/issues/2101#issuecomment-476869882",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>