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

terminate called after throwing an instance of 'std::bad_alloc' #136

Open
VERTlG0 opened this issue Mar 6, 2018 · 3 comments
Open

terminate called after throwing an instance of 'std::bad_alloc' #136

VERTlG0 opened this issue Mar 6, 2018 · 3 comments

Comments

@VERTlG0
Copy link

VERTlG0 commented Mar 6, 2018

Platform: GNU/Linux
Arch: Amd64
Kernel: 4.15.4
GCC: 5.4.0
btcpd version: Bitcoin Private Daemon version v1.0.10-1-9ee1d690

Thank you for running a Bitcoin Private node!You're helping to strengthen the network and contributing to a social good :)

In order to ensure you are adequately protecting your privacy when using
Bitcoin Private, please see https://z.cash/support/security/index.html.

       Block height | 281258
                   Connections | 4
                     Network solution rate | 26482089 Sol/s
                         Local solution rate | 0.0461 Sol/s

                         You are mining with the default solver on 1 threads.

                         Since starting this node 10 minutes, 16 seconds ago:
                         - You have validated 2907 transactions!
                         - You have completed 10 Equihash solver runs.
                         terminate called after throwing an instance of 'std::bad_alloc'
                           what():  std::bad_alloc
                           Aborted
@ch4ot1c ch4ot1c added the bug label Mar 28, 2018
@BlueSilver22
Copy link
Contributor

@jc23424 thoughts on this?

@ramphy
Copy link

ramphy commented May 27, 2018

@VERTlG0 Can you send a memory usage and other stats report?

@ch4ot1c
Copy link
Collaborator

ch4ot1c commented Jul 21, 2018

Need a debug log to investigate further. Certainly is a very rare issue / edge case. Regardless, the well-maintained Bitcoin codebase we are using in the rebase will have all these Zclassic-originated bugs squashed.

Please check out our progress, remembering it is not production ready: https://github.com/BTCPrivate/BTCP-Rebase

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

No branches or pull requests

4 participants