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
This error occurs during the POW mining phase, and at no specific block (seems random). Have not seen this happening when POW phase ends switching over to 100% POS.
One likely but not sure of possible culprit maybe this section of code:
char* result = reinterpret_cast<char*>(malloc(sizeof(char) * str.size()));
What brings to focus this part of code causing the problem is because on restart of the daemon, it fails warning of the database being corrupted, which after further investigating this lead to some hint from https://stackoverflow.com/a/26661206 that leveldb maybe the code responsible for this issue.
The text was updated successfully, but these errors were encountered:
DemonRx
changed the title
Error in `./COINd': realloc(): invalid next size: 0x00007f070c001490 #6
Error in `./COINd': realloc(): invalid next size: 0x00007f070c001490
Apr 13, 2019
@D3m0nKingx I don't see a problem with CopyString and it appears to be correct. Thanks for the report and please feel free to reopen this issue if you have any more reason to believe leveldb is the cause.
…with clang-cl" (google#673)
`MSVC` is true for clang-cl, but `"${CMAKE_CXX_COMPILER_ID}" STREQUAL
"MSVC"` is false, so we would enable -Wall, which means -Weverything
with clang-cl, and we get tons of undesired warnings.
Use the simpler condition to fix things.
Patch by: Reid Kleckner @rnk
OS: Ubuntu 16.04
Program: COINd (cryptocurrency daemon)
This error occurs during the POW mining phase, and at no specific block (seems random). Have not seen this happening when POW phase ends switching over to 100% POS.
One likely but not sure of possible culprit maybe this section of code:
leveldb/db/c.cc
Line 146 in 2f008ac
What brings to focus this part of code causing the problem is because on restart of the daemon, it fails warning of the database being corrupted, which after further investigating this lead to some hint from https://stackoverflow.com/a/26661206 that leveldb maybe the code responsible for this issue.
Error Produced:
The text was updated successfully, but these errors were encountered: