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

monero-wallet-rpc Wallet initialization failed: std::bad_alloc #1489

Closed
got3nks opened this issue Dec 22, 2016 · 4 comments
Closed

monero-wallet-rpc Wallet initialization failed: std::bad_alloc #1489

got3nks opened this issue Dec 22, 2016 · 4 comments
Labels

Comments

@got3nks
Copy link

got3nks commented Dec 22, 2016

After upgrading to v0.10.1 I can no longer load a wallet created with simplewallet (v0.9):


monero@server:~$ /home/monero/monero-wallet-rpc --rpc-bind-ip=0.0.0.0 --rpc-bind-port 8082 --password xxx --wallet-file /home/monero/wallet.bin --daemon-address=127.0.0.1:18081
Creating the logger system
Monero 'Wolfram Warptangent' (v0.10.1.0-release)
Logging at log level 0 to /home/monero/monero-wallet-rpc.log
2016-Dec-22 17:37:01.660812 Loading wallet...
2016-Dec-22 17:37:01.703471 Unknown refresh-type value (32767), using default
2016-Dec-22 17:37:01.703733 Loaded wallet keys file, with public address: xxxxxx
2016-Dec-22 17:37:03.603663 ERROR /DISTRIBUTION-BUILD/src/walle /wallet_rpc_server.cpp:1205 Wallet initialization failed: std::bad_alloc
@gituser
Copy link

gituser commented Dec 22, 2016

Just restore your wallet using seed or private key into new wallet file via monero-wallet-cli.

@dEBRUYNE-1
Copy link
Contributor

dEBRUYNE-1 commented Dec 29, 2016

This is caused by an incompatible wallet cache. If you delete the cache (<wallet>) you should be able to open the wallet created with simplewallet. If that doesn't work, use the method described by @gituser.

@vtnerd
Copy link
Contributor

vtnerd commented Dec 30, 2016

So this is most likely caused by a crazy allocation request when trying to parse in the new invalid format. Does the existing cache format have a header that can be used to identity between types? So that the code doesn't try to blindly attempt to parse the wrong format?

@dEBRUYNE-1
Copy link
Contributor

+resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants