Skip to content
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

Mempool fields in Debug Windows show "N/A" #17576

Closed
Relaxo143 opened this issue Nov 24, 2019 · 4 comments
Closed

Mempool fields in Debug Windows show "N/A" #17576

Relaxo143 opened this issue Nov 24, 2019 · 4 comments
Milestone

Comments

@Relaxo143
Copy link

Expected behavior
Show and update the number of txs in the mempool in real time

Actual behavior
Shows "N/A"

To reproduce
Tried restarting the node. reinstalling Core and running it without the .conf file. Issue persists. I'm not sure how to reproduce it.

System information

v0.19.0.1 downloaded from bitcoincore.org

Win10, Ryzen 5 2600, SSD

It happened after upgrading from 0.18.1 to 0.19.0.1
getrawmempool returns transactions, so the mempool is working. It appears to be a GUI issue
Screenshot_32

@Relaxo143 Relaxo143 added the Bug label Nov 24, 2019
@laanwj laanwj added the GUI label Nov 24, 2019
@laanwj
Copy link
Member

laanwj commented Nov 24, 2019

This will be fixed with #17427.

@mruddy
Copy link
Contributor

mruddy commented Nov 24, 2019

I see the same issue with the new release Bitcoin Core version v0.19.0.1 (release build). This is the command line that I used:

bitcoin-qt -txindex -datadir=/redacted -persistmempool=0 -server -rpcuser=redacted -rpcpassword=redacted

getmempoolinfo rpc does report seemingly correct data.

@laanwj laanwj added this to the 0.19.1 milestone Nov 24, 2019
@mjlamb
Copy link

mjlamb commented Nov 25, 2019

Hi reporting the same issue, both "Current number of transactions" and "Memory Usage" both = N/A, upgraded from v0.18.1 --> v0.19.0.1

@fanquake
Copy link
Member

Closing this, as the fix has been backported to the 0.19 branch in 2aba76c and a284bbb.

@bitcoin bitcoin locked as resolved and limited conversation to collaborators Dec 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants
@laanwj @fanquake @mjlamb @mruddy @Relaxo143 and others