-
Notifications
You must be signed in to change notification settings - Fork 271
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
New crash in v26.0 #785
Comments
@mzumsande wrote:
OK. I will install Qt5 packages with debug symbols and wait for it to crash again.
No, I don't think so. I only load 3 or 4 wallets on startup. Yesterday I tried loading around 100 old wallets that hadn't been loaded for a while. It took over 12 hours to load them all, but didn't crash. So it's not easy to trigger. I've only seen the crash twice, and both times it happened during the initial 'loading wallets' stage of startup. |
It seems you are running a prune node. Please with the logs, provide your bitcoin.conf values (hiding the sensitive information). |
This is what's in the pruned node's bitcoin.conf:
there's also a settings.json file that I didn't create I don't think. It says this:
|
That didn't take too long:
|
I'll leave the gdb session running for a few days in case there's anything helpful I can type at it. Let me know. |
It crashed again. This crash looks the same as the last one:
|
I just had this crash twice in a row. I was doing something specific both times. Maybe that's relevant: I had been using one of my wallets on a remote machine, and had a gap of about 30,000 unused addresses in the wallet, so some utxos weren't being shown up on the local wallet because my keypool was set to only 2500 or so. I shut down bitcoin-qt, thinking that I would edit keypool= in my bitcoin.conf and restart, but then I remembered there's an RPC call to refill the keypool to any size on demand, so I restarted bitcoin-qt without editing the bitcoin.conf and immediately ran "bitcoin-cli -rpcwallet=wallet keypoolrefill 30000" and that's when it crashed. I tried again, and it crashed ago. So I switched to using bitcoind instead of bitcoin-cli and it hasn't crashed since. Here are the 2 backtraces. They are very similar to each other, and to the ones I've posted before:
and
|
Is there an existing issue for this?
Current behaviour
bitcoin-qt crashed while loading wallets at startup.
I used to see occasional crashes on startup a few years ago, but it hasn't been happening at all in the last couple of major releases.
I've been running v26.0 for a week or two and haven't had any problem with it crashing until today.
Here's a backtrace. I run it in gdb habitually because I used to see a lot of crashes and never got around to changing that when it became more stable.
I configured with:
./configure CXXFLAGS=-fno-omit-frame-pointer --with-incompatible-bdb --with-miniupnpc=no --disable-debug
Expected behaviour
I expect it not to crash on startup...
Steps to reproduce
unknown
Relevant log output
How did you obtain Bitcoin Core
Compiled from source
What version of Bitcoin Core are you using?
v26.0
Operating system and version
Debian 12
Machine specifications
Linux, Intel, ssd, plenty of RAM
It happened again.
This node only connects to one other node. I run two nodes on the same machine. One connects to lots of peers, and this one that keeps crashing hosts my wallets, and only connects to the other node.
Moved from:
The text was updated successfully, but these errors were encountered: