-
Notifications
You must be signed in to change notification settings - Fork 64
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
Panic during block production: InsufficientFunds #2751
Comments
styppo
added a commit
that referenced
this issue
Aug 23, 2024
…on fails This should be removed once #2751 is fixed.
styppo
added a commit
that referenced
this issue
Aug 31, 2024
…on fails This should be removed once #2751 is fixed.
styppo
added a commit
that referenced
this issue
Aug 31, 2024
…on fails This should be removed once #2751 is fixed.
jsdanielh
pushed a commit
that referenced
this issue
Sep 2, 2024
…on fails This should be removed once #2751 is fixed.
jsdanielh
pushed a commit
that referenced
this issue
Sep 2, 2024
…on fails This should be removed once #2751 is fixed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A performance degradation was observed in the testnet after the spammer was started.
Block production /push times were high:
Also, validator 2 exhibited a behavior where from a certain point in time, it started accumulating all transactions in the mempool without removing any, which caused the mempool to get to its maximum capacity.
After dumping logs, the following panic was observed in validator 2:
ERROR panic | thread 'tokio-runtime-worker' panicked at 'Failed to compute accounts hash during block production: InsufficientFunds { needed: Coin(2), balance: Coin(0) }': blockchain/src/block_production/mod.rs:133 0: <backtrace::capture::Backtrace as core::default::Default>::default 1: log_panics::Config::install_panic_hook::{{closure}} 2: std::panicking::rust_panic_with_hook 3: std::panicking::begin_panic_handler::{{closure}} 4: std::sys_common::backtrace::__rust_end_short_backtrace 5: rust_begin_unwind 6: core::panicking::panic_fmt 7: core::result::unwrap_failed 8: nimiq_blockchain::block_production::BlockProducer::next_micro_block 9: nimiq_validator::micro::NextProduceMicroBlockEvent<TValidatorNetwork>::next::{{closure}} 10: <nimiq_validator::validator::Validator<TValidatorNetwork> as core::future::future::Future>::poll 11: <tokio_metrics::task::Instrumented<T> as core::future::future::Future>::poll 12: tokio::runtime::task::core::Core<T,S>::poll 13: tokio::runtime::task::harness::Harness<T,S>::poll 14: tokio::runtime::scheduler::multi_thread::worker::Context::run_task 15: tokio::runtime::scheduler::multi_thread::worker::Context::run 16: tokio::runtime::context::set_scheduler 17: tokio::runtime::context::runtime::enter_runtime 18: tokio::runtime::scheduler::multi_thread::worker::run 19: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll 20: tokio::runtime::task::core::Core<T,S>::poll 21: tokio::runtime::task::harness::Harness<T,S>::poll 22: std::sys_common::backtrace::__rust_begin_short_backtrace 23: core::ops::function::FnOnce::call_once{{vtable.shim}} 24: std::sys::pal::unix::thread::Thread::new::thread_start 25: <unknown> 26: <unknown>
The text was updated successfully, but these errors were encountered: