Skip to content
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

Closed
shane-kerr opened this issue May 28, 2018 · 8 comments
Labels
bug Windows Problems with the wallet on Windows

Comments

@shane-kerr
Copy link
Member

Many Windows users have reported:

EXCEPTION: St9bad_alloc
std::bad_alloc
C:\Users\Papa\Desktop\MintCoin-Qt.exe in Runaway exception

A workaround for now is:

  • Make a shortcut to Mintcoin-Qt.exe
  • Right click on the shortcut->Properties. Then add -splash=0 to the end of the target string.

We should find and fix the underlying issue though.

@gradegal
Copy link

thanks for the workaround - now this exception doesn`t show up again - but the wallet gets no connections to network.

debug.log

@shane-kerr
Copy link
Member Author

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

@gradegal
Copy link

....but for now you need to specify nodes directly using addnode.

How can I do this ?

@Myke500
Copy link

Myke500 commented Jul 23, 2018

Getting a slightly different error
EXCEPTION: St13runtime_error
CDE(): error opening database environment IO error:

Same or needs new issue thread?
merror

@shane-kerr
Copy link
Member Author

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:

https://docs.microsoft.com/en-gb/windows/desktop/Memory/memory-limits-for-windows-releases#memory_limits

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.

@shane-kerr
Copy link
Member Author

shane-kerr commented Aug 13, 2018

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.

@gradegal
Copy link

gradegal commented Aug 14, 2018 via email

@shane-kerr
Copy link
Member Author

This is fixed with the release of the 2.1 wallet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Windows Problems with the wallet on Windows
Projects
None yet
Development

No branches or pull requests

3 participants