forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Reproducible Access Violation while reindexing with litecoin-qt.exe on windows #945
Comments
Reindexing with v0.17.1 seemed to work well.Also opening afterwards with v0.21.2.2 worked but debug.log showed errors which don't look good:
Rolling back to the data from after reindexing with v0.17.1 and trying with v0.18.1.No errors but a lot of warnings in the debug.log:
The GUI also shows a warning below the menu:
Shutting down and trying with the direct jump from v0.17.1 to v0.21.2Same errors in the debug.log again:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to reindex with the following command
litecoin-qt.exe -reindex
or
litecoind.exe -reindex
and the process deterministically crashes with
Exception thrown at 0x0000000000DA9A23 in litecoin-qt.exe: 0xC0000005: Access violation reading location 0x0000000000000004.
and the state:
I'll try to downgrade the client and will add info here.
Expected behavior
No access violation
Actual behavior
Exception thrown at 0x0000000000DA9A23 in litecoin-qt.exe: 0xC0000005: Access violation reading location 0x0000000000000004.
in state:
with both, v0.21.2.2 and v0.21.2
To reproduce
run the command
litecoin-qt.exe -reindex
Can reliably reproduce every time.
litecoin.conf
is empty.System information
Tested so far with
from https://github.com/litecoin-project/litecoin/releases
on
extra info
The debug.log doesn't show the exception.
Its last entry is
2024-03-10T15:43:40Z UpdateTip: new best=fd4bc7ebe60a72248aa218de4caf82f6fd32a9613331f34beea9980059b7b00d height=1261660 version=0x20000000 log2_work=67.564697 tx=11494846 date='2017-08-20T12:34:02Z' progress=0.063369 cache=85.4MiB(227175txo)
The process just silently dies. I looked at the dumps and attached Visual Studio to see the exception.
It might be helpful to get the PDBs of the build to narrow down the location but i couldn't find them and haven't succeeded creating my own build yet.
Couldn't find the
config.log
.The text was updated successfully, but these errors were encountered: