<p></p>
<blockquote>
<p>Yeah but I was wondering about <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/lmforget/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/lmforget">@lmforget</a>, <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/Bergamask/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Bergamask">@Bergamask</a> and <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/Chicopower/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Chicopower">@Chicopower</a> who had problems with the original 1.37 installer but got it working with the "-2" installer. This might indicate there was additionally an independent problem.</p>
</blockquote>
<p>As <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/Chicopower/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Chicopower">@Chicopower</a> said, they might all have tried something else in between and then had the config file and wouldn't hit the issue.<br>
But even if they did not, I wouldn't be totally surprised if another set of libraries did not lead to a crash.  I'm not sure how Windows behaves in this regard, but usually reading arbitrary memory like this leads to unpredictable results, not necessarily a crash. Could be that that other set of libraries result in a memory mapping with a zero byte (string terminator) close to the address that gets read before hitting a memory violation.  Or maybe not, but well, I wouldn't bet anything on that horse.  My point is: don't sweat it looking for another problem yet, it's more than likely that <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="738227119" data-permission-text="Title is private" data-url="https://github.com/geany/geany/issues/2645" data-hovercard-type="pull_request" data-hovercard-url="/geany/geany/pull/2645/hovercard" href="https://github.com/geany/geany/pull/2645">#2645</a> is the answer.  But sure, getting them to try the version with the meaningful fix is a good idea for sure, then we'll have a better idea :)</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/2639#issuecomment-723498885">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ226QFF7FR5IQNWDF3SOW5RPANCNFSM4TGHN3OA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AAIOWJ4XKLDZ242PPPMHWEDSOW5RPA5CNFSM4TGHN3OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFMP3PBI.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/2639#issuecomment-723498885",
"url": "https://github.com/geany/geany/issues/2639#issuecomment-723498885",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>