You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did a git pull of this repo this afternoon and build merit v0.5.6.0-d7a6129 on my Ubuntu 16.04 laptop. Next, I fired up merit-qt from a console window and starting mining. Since I didn't add the & to detach from the console, it stayed open and attached to the merit-qt process, which ran fine. After leaving for about two hours, I returned to find merit-qt gone and the following assertion in the console window:
No. I ran merit-qt the same way again and it synced up the two hours of blocks, and then I started mining again without issue. Before I did this, I did back up my ~/.merit directory just in case it might hold something useful. I will leave merit-qt running and mining overnight and will update this report if it asserts again.
What version of merit-core are you using?
Self-compiled v0.5.6.0-d7a6129 .
Machine specs:
OS: Ubuntu 16.04
CPU: Intel Core i7-3610QM
RAM: 15/6 GiB according to Ubuntu
Disk size: 500GB
Disk Type (HD/SDD): HD
The text was updated successfully, but these errors were encountered:
Describe the issue
I did a git pull of this repo this afternoon and build merit v0.5.6.0-d7a6129 on my Ubuntu 16.04 laptop. Next, I fired up merit-qt from a console window and starting mining. Since I didn't add the & to detach from the console, it stayed open and attached to the merit-qt process, which ran fine. After leaving for about two hours, I returned to find merit-qt gone and the following assertion in the console window:
merit-qt: cuckoo/mean_cuckoo.cpp:952: void edgetrimmer<offset_t, EDGEBITS, XBITS>::trimrename1(uint32_t, uint32_t) [with bool TRIMONV = false; offset_t = unsigned int; unsigned char EDGEBITS = 26u; unsigned char XBITS = 5u; uint32_t = unsigned int]: Assertion `maxnnid < P::NYZ2' failed.
Can you reliably reproduce the issue?
No. I ran merit-qt the same way again and it synced up the two hours of blocks, and then I started mining again without issue. Before I did this, I did back up my ~/.merit directory just in case it might hold something useful. I will leave merit-qt running and mining overnight and will update this report if it asserts again.
What version of merit-core are you using?
Self-compiled v0.5.6.0-d7a6129 .
Machine specs:
The text was updated successfully, but these errors were encountered: