> Yeah but I was wondering about @lmforget, @Bergamask and @Chicopower 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.
As @Chicopower said, they might all have tried something else in between and then had the config file and wouldn't hit the issue. 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 #2645 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 :) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2639#issuecomment-723498885
