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

potential memory leak #270

Open
Gingeropolous opened this issue May 19, 2022 · 10 comments
Open

potential memory leak #270

Gingeropolous opened this issue May 19, 2022 · 10 comments

Comments

@Gingeropolous
Copy link
Contributor

xmrchain runs on a box with 64 gb ram. using top, it shows that the mainnet explorer (the one that gets the most traffic) ends up with 74% memory utilization over time. I occasionally restart it because that amount seems absurd with how clean everything looks and feels with the explorer. After restart, its back at < 5% or so.

Any thoughts on how I could help hunt this down? Perhaps right around a HF is not the time for this, but just wanted to let you know in case I haven't already.

@moneroexamples
Copy link
Owner

Did it start happening with new changes in the explorer introduced for the upcoming HF?

@Gingeropolous
Copy link
Contributor Author

no, its been going on ever since I've been running xmrchain honestly. I just haven't really been concerned because restarting it "fixes" it, and it seems to run fine, so I didn't think it was critical.

so its been running since i made that first post above. and once again its at 75% memory.

@moneroexamples
Copy link
Owner

Can you try running it bear bones, without any extra options like --enable-emission-monitor, --enable-autorefresh-option, --enable-pusher, etc?

@Gingeropolous
Copy link
Contributor Author

well if i kill the api then some stupid services that don't understand decentralization will stop working, so i'll do everything except that.

@moneroexamples
Copy link
Owner

Ok. I will try to run the explorer and simulate the high traffic, and see how it goes.

@Gingeropolous
Copy link
Contributor Author

well i ran it with only the API, and its currently at 57% ram

@moneroexamples
Copy link
Owner

Still lots. Could you share the settings/options that you use for the explorer?

@Gingeropolous
Copy link
Contributor Author

this is what i normally run:

./xmrblocks -p 8888
--enable-pusher 1
--enable-key-image-checker 1
--enable-output-key-checker 1
--enable-autorefresh-option 1
--enable-json-api 1
--deamon-url http:://127.0.0.1:12345
--testnet-url https://testnet.xmrchain.net/
--stagenet-url https://stagenet.xmrchain.net/
--mainnet-url https://xmrchain.net/
--enable-mixin-details 1
--enable-emission-monitor 1
--enable-randomx

Can I revert my settings to the ones above, or do you still need me to run it minimal?

@moneroexamples
Copy link
Owner

You can run it normally. I will try to investigate what's happening with and without those settings.

@DaWe35
Copy link
Contributor

DaWe35 commented Feb 28, 2024

Another possible memory-leak related issue: #308

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants