Version 11+ makes Windows 10 unusable / memory leak #748
Comments
|
Had you run a previous build? Did you remove everything from the data dir or just the data.ldb and could you restart the computer, clear out the data dir and try again if you haven't already |
|
yes, it doesn't matter. just tried again and have to hard reset my machine |
|
Based on the number of accounts out of sync it looks like this is a fresh install. Have you run previous versions on this machine? |
|
yes, since version 8, but since starting milestone 11 crashed, I decided to wipe the databases and wallet files and try again, without reusing the database that was working from previous versions |
|
Can you try this version instead and let me know what the results, You should uninstall the previous and reinstall with this one. |
|
sorry for the delay on the response. I'm trying 11.1 right now and will report back. so far, it says it's synchronizing without the lockup, and using my previous seed without any issue
EDIT: although the problem with #227 persists |
|
ok, it seems that it's stuck forever on Block 1, even from a fresh start. the block count keep growing, the database file is 1,7GB, but it's just "frozen" in time, although the GUI is responsive. issue #635 still happens (closed it, and the process is in the background doing nothing, but using more and more memory each time it passes)
|
|
what did the unchecked count get to? chances are the blocks needing to be processed to continue with the bootstrapping had not been received yet and as a result would act as a blocker to checking in further blocks. The process still running after exit is still being investigated |
|
it was around 3,8kk and the process is still stuck , and eventually will memory leak until my system crashes
|
|
Does the memory leak only start when you exit? |
|
yes, while it was opened, the memory was stable, but the UI wasn't doing anything |
|
also 3.8kk is only about half downloaded, that would explain why you werent getting past 1 if it hadnt downloaded the block yet. You may want to wait for all almost 7.3m blocks to download as it could be the very last block you download that is needed to continue checking in blocks |
|
well, that's really counter productive. anyway, the process is memory leaking and nearing 2GB, I'll have to kill it
|
|
It sounds like you’re running it on a machine with slow disk IO. If it can't write to disk fast enough it keeps it in memory. Improving disk IO is slowly coming to the top of the list of things to work on, there have been other higher priority issues. |
|
I'm on a Samsung EVO 850 👍
|
|
Odd, then I haven’t seen a memory spike like that, we’ll have to see what it takes to reproduce. |
|
how much memory does it show as using while its running and stable? |
|
@argakiig this is the usual memory usage
that's why it's a clear indication of a serious memory leak EDIT: now that it started processing the blocks, although higher, the memory is stable around 800MB
|
|
It’s be interesting to know what it stabilizes to. When I run it on OSX it’s pretty stable around 70-120. I’ve seen it spike on systems that have bad disk IO as it puts blocks in memory until written to disk but with that SSD that’s clearly not the case. |
|
yeah, the I/O isn't high, that's why it's strange, maybe it's an Windows issue, I decided to monitor the disk activity and it seems fine, no crazy reads or writes, it tops around 10MB/s, averaging 2MB/s, so it's clearly not an I/O issue. average response time is 3ms. it's fairly constant as expected, the only issue is when you close the wallet
don't know what else to look for. I'm in a older system besides the SSD though (Core 2 Quad Q9550 and 8 GB of DDR2 800) but have no issues with, for example, Bitcoin Core or other more intensive / aggressive / non-optimized coins, like Ethereum |
|
still synchronizing, really really slow, on 2,6kk blocks (being more than 24 hours already), and slowing whole Windows down. I won't be able to work with the wallet opened... text editors lag, sound is glitching, makes the whole system unresponsive from time to time. nothing wrong in the logs, besides the republish infos: |
pocesar
changed the title
pocesar
changed the title
|
This should be resolved by the memory leak fixes supplied in V17.0 ! See #1338 for additional details. |
Description of bug:
Wallets starts briefly, then freezes, database size stays the same
Steps to reproduce the issue:
Describe the results you received:
Windows Error Reporting starts using 100% (on one core), and is unkillable.
the only way to stop this is forcefully restarting the computer (taskkill can't kill it)
Describe the results you expected:
It works like previous versions
Additional information you deem important (e.g. issue happens only occasionally):
Happened every time, from the 3 times I tried
Environment:
logs
The text was updated successfully, but these errors were encountered: