Synchronization stopped. Can't connect anymore.

[Juggernaut0000]

Detail of the issue

Was able to sync about 35% of the blocks.
The next time I ran the Neuron wallet, it got stuck on 'connecting', and has not connected since.
Tried clearing the cache, restarting the wallet, restarting pc, etc etc.

Neuron Version: 0.110.1
CKB Clien Version: v0.110.0

Added the 3 logs to a zip, providing it below gets me an error message saying "the body is too long".
neuron_debug_1687285001305.zip

bundled-ckb.log

No response

main.log

No response

status.log

No response

[Keith-CY]

Hi @Juggernaut0000

The bundled-ckb.log shows the following log

2023-06-20 18:15:50.316 +00:00 main INFO ckb_launcher  Miner is disabled, edit ckb.toml to enable it
2023-06-20 18:15:51.701 +00:00 main INFO ckb_memory_tracker::process  track current process: unsupported
2023-06-20 18:15:51.703 +00:00 main INFO ckb_launcher  chain genesis hash: 0x92b197aa1fba0f63633922c61c92375c9c074a93e85963554f5499fe1450d0e5
2023-06-20 18:15:51.703 +00:00 main INFO ckb_sync::types  header_map.memory_limit 600MB
2023-06-20 18:16:19.936 +00:00 main INFO ckb_bin::subcommand::run  ckb version: 0.110.0 (0679b11 2023-05-16)
2023-06-20 18:16:19.937 +00:00 main INFO ckb_launcher  Miner is disabled, edit ckb.toml to enable it
2023-06-20 18:16:21.835 +00:00 main INFO ckb_memory_tracker::process  track current process: unsupported
2023-06-20 18:16:21.836 +00:00 main INFO ckb_launcher  chain genesis hash: 0x92b197aa1fba0f63633922c61c92375c9c074a93e85963554f5499fe1450d0e5
2023-06-20 18:16:21.836 +00:00 main INFO ckb_sync::types  header_map.memory_limit 600MB

It's been confirmed as a performance issue of the built-in CKB node that it requires too much computer memory, and can be workarounded by the method mentioned at #2699 (comment)

The performance issue will be resolved in the future.

[Juggernaut0000]

Thanks. Relocating 'addr_manager.db' did the trick.

Don't really get that it requires too much computer memory.
I have 16 GB's of it, but it doesn't want to use it...
It uses at most 1.1 GB of RAM

[Keith-CY]

Thanks. Relocating 'addr_manager.db' did the trick.

Don't really get that it requires too much computer memory. I have 16 GB's of it, but it doesn't want to use it... It uses at most 1.1 GB of RAM

It's beyond what I've learned, and I will send the core team this case as a reference to fix this issue.

[Juggernaut0000]

Many thanks, Keith.
Have a great day.

[Juggernaut0000]

Update: I've noticed it has ramped up the RAM usage since it started syncing again, now it's up to 3.3 GB's.

[github-actions]

Mark this issue stale because no activity for 60 days

[github-actions]

Close this issue because it's inactive since marked stale