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

[TestNet] Sync using current master (6412e735) stalled for hours #3602

Closed
Gandalf-the-Grey opened this issue Feb 8, 2020 · 4 comments
Closed

Comments

@Gandalf-the-Grey
Copy link
Contributor

While syncing with current instance of testnet (
It stays on:

  "head_block_number": 100827,
  "head_block_id": "000189db42e04ea975e12cd3d34f15b69cf74bde",
  "time": "2020-02-05T18:07:39",
  "current_witness": "init-0",

for hours with CPU being used all the time.

@Gandalf-the-Grey
Copy link
Contributor Author

Possibly duplicate of #3589 except that for my case (non-MIRA) it seems to take at least 12 hours (I wasn't patient enough to keep it running for a longer time)

@mvandeberg
Copy link
Contributor

Can you run it again and profile to see where it is spending time?

@Gandalf-the-Grey
Copy link
Contributor Author

Sure :-)

steem::plugins::chain::detail::chain_plugin_impl::start_write_processing()::{lambda()#1}::operator()() const
                                    |
                                    |
                                   \|/
bool boost::lockfree::queue<steem::plugins::chain::write_context*>::pop<steem::plugins::chain::write_context*>(steem::plugins::chain::write_context*&)

call_graph

@mvandeberg
Copy link
Contributor

master has serialization changes not present on the public testnet. It will work when the testnet is redeployed.

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

No branches or pull requests

2 participants