-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EXCEPTION: St9bad_alloc std::bad_alloc C:\Users\Papa\Desktop\MintCoin-Qt.exe in Runaway exception #67
Comments
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 (Windows) https://www.youtube.com/watch?v=bc7FecSGm1s |
....but for now you need to specify nodes directly using addnode. How can I do this ? |
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 |
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 ***@***.***>:
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.
The text was updated successfully, but these errors were encountered: