search

biblepay / biblepay_legacy

BiblePay
MIT License
35 stars 34 forks source link

Random QT wallet crashes 1187/1188 #76

Closed fogoat closed 5 years ago

fogoat commented 5 years ago

Discord users are reporting random QT wallet crashes. Unable to get better details, but it is happening for some users, sometimes.

biblepay commented 5 years ago

Im merging MIPs fix into prod now; please let me know if this is fixed when we release 1189.

fogoat commented 5 years ago

1189 wallet crashed. Not running PoG on the wallet, but controls a MN and PoDC.

Last several lines from debug.log:

2019-02-19 17:57:45 ProcessNewBlock : ACCEPTED 2019-02-19 17:57:58 DSTX -- Got Masternode transaction 108b1de7f660492e7dc32c97af6393df6d2d9a549033ebcd134a9bd0b62f3da5 2019-02-19 17:57:58 PrioritiseTransaction: 108b1de7f660492e7dc32c97af6393df6d2d9a549033ebcd134a9bd0b62f3da5 priority += 1000.000000, fee += 0.10 2019-02-19 17:57:58 DSTX -- Masternode transaction accepted, txid=108b1de7f660492e7dc32c97af6393df6d2d9a549033ebcd134a9bd0b62f3da5, peer=17 2019-02-19 17:58:11 DSTX -- Got Masternode transaction bc8dd87a50fa37626278538b019dd24637d777e1ed2c36f76f6125f57a1fd27a 2019-02-19 17:58:11 PrioritiseTransaction: bc8dd87a50fa37626278538b019dd24637d777e1ed2c36f76f6125f57a1fd27a priority += 1000.000000, fee += 0.10 2019-02-19 17:58:11 DSTX -- Masternode transaction accepted, txid=bc8dd87a50fa37626278538b019dd24637d777e1ed2c36f76f6125f57a1fd27a, peer=73 2019-02-19 17:59:31 UpdateTip: new best=c9799881ca6a242afaa587433d4a675859c94686cb0dc53fafa827de25cfccc9 height=102522 log2_work=59.180694 tx=846901 date=2019-02-19 17:59:31 progress=1.000000

MIPPL commented 5 years ago

I guess you already tried to rescan and repair wallet.dat with zapwallettxes=1 did you?

biblepay commented 5 years ago

Sorry to put you through this Sun, but this is the only way I know how we can catch this... Could we please have you compile the source code version of biblepay, and run biblepay in valgrind like this: cd ~/biblepay/src/qt valgrind ./biblepay-qt

If you just leave it run til it crashes again, you can then give us the line # and module filename.

MIP and I are also going to try to catch that. It appears to be something to do with a sanctuary is running with an invalid keypair and either cant sign the instantsend or possibly when you or I receive the vote, we crash the node. But we need the line # in order to pinpoint why the node segfaulted.

Btw, you cant run valgrind on a binary (you can but it is useless to us). It must be run on a compiled source.