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

Restore from seed words when DAO enabled cause CPU peak #2425

Closed
ManfredKarrer opened this issue Feb 15, 2019 · 8 comments
Closed

Restore from seed words when DAO enabled cause CPU peak #2425

ManfredKarrer opened this issue Feb 15, 2019 · 8 comments
Assignees

Comments

@ManfredKarrer
Copy link
Member

There seem to be an issue when restoring from seed words at least in one data directory from @devinbileck from testnet.
App is frozen for quite long, restore seems to work but closing the app does not work anymore.
Maybe it is related to the DAO as it only happened on testnet with an app which had many DAO transactions.

@ManfredKarrer
Copy link
Member Author

Yes it is DAO related, after deactivating the DAO the wallet restore was quickly done but still closing the app does not work.

@ManfredKarrer ManfredKarrer changed the title Restore from seed words takes very long Restore from seed words when DAO enabled cause CPU peak Feb 15, 2019
@devinbileck
Copy link
Member

May be related to #2415

@ripcurlx ripcurlx added the a:bug label Feb 18, 2019
@oscarguindzberg
Copy link
Contributor

Maybe related to #1823 (comment)

@ManfredKarrer
Copy link
Member Author

ManfredKarrer commented Feb 19, 2019

Testnet has atm crazy block confirmation time (seems some ascis are point to testnet), about 15 sec. So lots of blocks are created in short time, which mimics the situation as if the user was not online for several months and need to sync up. Still investigating but the perfromance issue is happening only with old testnet wallets as far I see.

@ManfredKarrer
Copy link
Member Author

I think that issue was mainly caused by crazy testnet block creation time. I will close here as the other possible issues are covered anyway in other issues.

@devinbileck
Copy link
Member

I still encounter this issue on DAO testnet.

@ManfredKarrer ManfredKarrer reopened this Mar 4, 2019
@ManfredKarrer
Copy link
Member Author

@devinbileck Can you still reproduce it? The issue on testnet might have been related to the huge amount of blocks they created....

I cannot reproduce it on regtest or dao-betanet.

@devinbileck
Copy link
Member

I cannot reproduce this on dao betanet nor on dao testnet.
Potentially due to now that it forces a shutdown?

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