Closed shane-kerr closed 6 years ago
thanks for the workaround - now this exception doesn`t show up again - but the wallet gets no connections to network.
The code in the GitHub repository has a fix for not getting connections, but for now you need to specify nodes directly using addnode
. You may find one of these videos helpful:
(Windows) https://www.youtube.com/watch?v=bc7FecSGm1s (Mac) https://www.youtube.com/watch?v=yn4M_H69ZP8 (Mac Lion to High Sierra) https://www.youtube.com/watch?v=MQY1KOyu8uY
....but for now you need to specify nodes directly using addnode.
How can I do this ?
Getting a slightly different error EXCEPTION: St13runtime_error CDE(): error opening database environment IO error:
Same or needs new issue thread?
It seems that we were running up into the default 2 GB process size limit for 32-bit applications in Windows. 32-bit applications running in 32-bit Windows can support up to 3 GB of RAM, and 32-bit applications running in 64-bit Windows can support up too 4 GB of RAM, but they need to be compiled with this feature enabled.
Here's the Microsoft page about this build option, IMAGE_FILE_LARGE_ADDRESS_AWARE, for your reading pleasure:
In our case we are using the MXE cross-compile from Linux, and need to add the -Wl,--large-address-aware
flag to our 32-bit Windows build.
This seems to be fixed with binaries built by Travis, using the linker options which set the binaries to support 3 GB of RAM, which we will use for the next release.
I'll keep this ticket open to point people to until then.
Dear Shane, thank you very much for this update 👍🏼 I am eager for the next release of the wallet.
Am 13.08.2018 um 23:37 schrieb Shane Kerr notifications@github.com:
This seems to be fixed with binaries built by Travis, which we will use for the next release.
I'll keep this ticket open to point people to until then.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
This is fixed with the release of the 2.1 wallet.
Many Windows users have reported:
A workaround for now is:
-splash=0
to the end of the target string.We should find and fix the underlying issue though.