Multipe issues with plugins

[PsySc0rpi0n]

This started with cln-rest plugin which was killing itself after normal operation.

Bitcoin Core version

$ bitcoin-cli --version
Bitcoin Core RPC client version v28.0
Copyright (C) 2009-2024 The Bitcoin Core developers

Please contribute if you find Bitcoin Core useful. Visit
<https://bitcoincore.org/> for further information about the software.
The source code is available from <https://github.com/bitcoin/bitcoin>.

This is experimental software.
Distributed under the MIT software license, see the accompanying file COPYING
or <https://opensource.org/licenses/MIT>

Core Lightning version:

$ lightning-cli --version
v25.09-474-g8732410

Core Lightning config file

$ cat ~/.lightning/config 

network=bitcoin
bitcoin-cli=/home/psysc0rpi0n/Downloads/bitcoin/src/bitcoin-cli
bitcoin-datadir=/home/psysc0rpi0n/.bitcoin
# debug
log-level=debug:sling
log-file=/home/psysc0rpi0n/.lightning/debug.log

alias=Crypt04n4rkMoV
rgb=ffff00
watchtime-blocks=720
wallet=sqlite3:///home/psysc0rpi0n/.lightning/bitcoin/lightningd.sqlite3:/media/MyBook/c-lightning/advancedDB/lightningd.sqlite3

proxy=127.0.0.1:9050
bind-addr=127.0.0.1:9735
announce-addr=2obm3yvfj5m3zabnea5y2xolimeuc4gbelika3pa7div5pk2eolqrtad.onion
always-use-proxy=true
min-capacity-sat=400000

# liquidity avertisement
experimental-dual-fund
funder-policy=match
funder-policy-mod=100
lease-fee-basis=10
channel-fee-max-base-msat=1250msat
channel-fee-max-proportional-thousandths=1
funder-lease-requests-only=false

#Plugins section
plugin=/home/psysc0rpi0n/Downloads/sling/target/release/sling

# New CLN Rest plugin
clnrest-port=3010

Logs that I have for the cln-rest issue:

2025-12-03T10:56:03.659Z DEBUG   plugin-sling: Refreshed graph in 61ms!
2025-12-03T10:56:07.176Z INFO    plugin-clnrest: Authorized rune_id:`5` access to method:`listforwards` with params:`{"status":"failed"}`
2025-12-03T10:56:10.027Z INFO    plugin-clnrest: Authorized rune_id:`5` access to method:`getinfo` with params:`{}`
2025-12-03T10:56:10.349Z INFO    plugin-clnrest: Authorized rune_id:`5` access to method:`listfunds` with params:`{}`
2025-12-03T10:56:10.352Z INFO    plugin-clnrest: Authorized rune_id:`5` access to method:`listinvoices` with params:`{}`
2025-12-03T10:56:10.565Z INFO    plugin-clnrest: Authorized rune_id:`5` access to method:`feerates` with params:`{"style":"perkw"}`
2025-12-03T10:56:10.565Z INFO    plugin-clnrest: Authorized rune_id:`5` access to method:`feerates` with params:`{"style":"perkb"}`
2025-12-03T10:56:10.569Z INFO    plugin-clnrest: Authorized rune_id:`5` access to method:`listpeers` with params:`{}`
2025-12-03T10:56:10.570Z INFO    plugin-clnrest: Authorized rune_id:`5` access to method:`listpeerchannels` with params:`{}`
2025-12-03T10:56:10.570Z INFO    plugin-clnrest: Authorized rune_id:`5` access to method:`listsendpays` with params:`{}`
2025-12-03T10:56:13.706Z DEBUG   plugin-sling: Getting all channels in gossip_store...
2025-12-03T10:56:13.707Z DEBUG   plugin-sling: read_gossip_file: built 0/0 new channels
2025-12-03T10:56:13.708Z DEBUG   plugin-sling: Reading gossip store done after 12ms!
2025-12-03T10:56:13.709Z DEBUG   plugin-sling: 77405 public channels in sling graph after 25ms!
2025-12-03T10:56:13.709Z DEBUG   plugin-sling: Got 4 local channels after 25ms!
2025-12-03T10:56:13.710Z DEBUG   plugin-sling: 0 private channels in sling graph after 49ms!
2025-12-03T10:56:13.710Z DEBUG   plugin-sling: Refreshed graph in 49ms!
2025-12-03T10:56:23.776Z DEBUG   plugin-sling: Getting all channels in gossip_store...
2025-12-03T10:56:23.777Z DEBUG   plugin-sling: read_gossip_file: built 0/0 new channels
2025-12-03T10:56:23.778Z DEBUG   plugin-sling: Reading gossip store done after 21ms!
2025-12-03T10:56:23.778Z DEBUG   plugin-sling: 77405 public channels in sling graph after 38ms!
2025-12-03T10:56:23.778Z DEBUG   plugin-sling: Got 4 local channels after 39ms!
2025-12-03T10:56:23.778Z DEBUG   plugin-sling: 0 private channels in sling graph after 68ms!
2025-12-03T10:56:23.779Z DEBUG   plugin-sling: Refreshed graph in 68ms!
2025-12-03T10:56:33.835Z DEBUG   plugin-sling: Getting all channels in gossip_store...
2025-12-03T10:56:33.837Z DEBUG   plugin-sling: read_gossip_file: built 0/0 new channels
2025-12-03T10:56:33.837Z DEBUG   plugin-sling: Reading gossip store done after 14ms!
2025-12-03T10:56:33.838Z DEBUG   plugin-sling: 77405 public channels in sling graph after 29ms!
2025-12-03T10:56:33.838Z DEBUG   plugin-sling: Got 4 local channels after 29ms!
2025-12-03T10:56:33.839Z DEBUG   plugin-sling: 0 private channels in sling graph after 58ms!
2025-12-03T10:56:33.839Z DEBUG   plugin-sling: Refreshed graph in 58ms!
2025-12-03T10:56:35.915Z INFO    plugin-clnrest: Killing plugin: exited during normal operation
2025-12-03T10:56:35.916Z **BROKEN** plugin-clnrest: Plugin marked as important, shutting down lightningd!
2025-12-03T10:56:35.920Z INFO    03ec0f6f9ba5d21c254299dd83760beb6bff3fa0826bc2fd6cd6c8f0783308f812-chan#114: Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (9)
2025-12-03T10:56:35.921Z INFO    03c5254c74e21a342f4182e5993dafe164527a42340a301dd5736b9a3017701013-chan#117: Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (9)
2025-12-03T10:56:35.922Z INFO    02beb608b225320db6b5a1204ec91c18234e88efee7cb38342d66d9d0e2aebcc91-chan#112: Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (9)
2025-12-03T10:56:35.923Z INFO    02d96eadea3d780104449aca5c93461ce67c1564e2e1d73225fa67dd3b997a6018-chan#113: Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (9)
2025-12-03T10:56:35.982Z DEBUG   plugin-sling: Got shutdown notification
2025-12-03T10:56:35.982Z DEBUG   plugin-sling: Wrote liquidity to disk in 2ms 
2025-12-03T10:56:36.011Z DEBUG   plugin-sling: Killing plugin: exited during normal operation

This already happened like 2 or 3 times in the past 10~12 days, maybe...

Then, toay, I had a Core Lightning crash that I will also paste here te log of it. Not sure it's the best idea to put here the crash but maybe it could be related. If it's totally unrelated, I'll delete it later.

2025-12-04T04:55:00.579Z DEBUG   plugin-sling: 77391 public channels in sling graph after 35ms!
2025-12-04T04:55:00.579Z DEBUG   plugin-sling: Got 4 local channels after 35ms!
2025-12-04T04:55:00.579Z DEBUG   plugin-sling: 0 private channels in sling graph after 63ms!
2025-12-04T04:55:00.579Z DEBUG   plugin-sling: Refreshed graph in 63ms!
2025-12-04T04:55:00.637Z INFO    plugin-sling: Refreshed 0 liquidity beliefs in 0ms!
2025-12-04T04:55:07.554Z INFO    plugin-keysend: Killing plugin: exited during normal operation
2025-12-04T04:55:07.554Z **BROKEN** plugin-keysend: Plugin marked as important, shutting down lightningd!
2025-12-04T04:55:07.559Z INFO    02d96eadea3d780104449aca5c93461ce67c1564e2e1d73225fa67dd3b997a6018-chan#113: Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (1)
2025-12-04T04:55:07.559Z INFO    plugin-funder: Killing plugin: exited during normal operation
2025-12-04T04:55:07.559Z **BROKEN** plugin-funder: Plugin marked as important, shutting down lightningd!
2025-12-04T04:55:07.564Z INFO    plugin-summary.py: Killing plugin: exited during normal operation
2025-12-04T04:55:07.566Z INFO    plugin-monitor.py: Killing plugin: exited during normal operation
2025-12-04T04:55:07.566Z INFO    plugin-bcli: Killing plugin: exited during normal operation
2025-12-04T04:55:07.567Z **BROKEN** lightningd: The Bitcoin backend died.
2025-12-04T04:55:07.883Z **BROKEN** lightningd: FATAL SIGNAL 6 (version v25.09-474-g8732410)
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: common/daemon.c:46 (send_backtrace) 0xaaaac02b607b
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: common/daemon.c:83 (crashdump) 0xaaaac02b60d3
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0xffff853657bb
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ./nptl/pthread_kill.c:44 (__pthread_kill_implementation) 0xffff84ee3c18
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ../sysdeps/posix/raise.c:26 (__GI_raise) 0xffff84e9a8ab
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ./stdlib/abort.c:79 (__GI_abort) 0xffff84e8747f
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: lightningd/log.c:1054 (fatal_vfmt) 0xaaaac022726b
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: lightningd/log.c:1064 (fatal) 0xaaaac02272ff
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: lightningd/bitcoind.c:27 (bitcoin_destructor) 0xaaaac01f4697
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/tal/tal.c:246 (notify) 0xaaaac030a863
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/tal/tal.c:437 (del_tree) 0xaaaac030a94f
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/tal/tal.c:532 (tal_free) 0xaaaac030af77
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: lightningd/plugin.c:469 (plugin_kill) 0xaaaac02502c7
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: lightningd/plugin.c:861 (plugin_conn_finish) 0xaaaac02505d3
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/io/poll.c:246 (destroy_conn) 0xaaaac02fdb0b
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/io/poll.c:252 (destroy_conn_close_fd) 0xaaaac02fdb37
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/tal/tal.c:246 (notify) 0xaaaac030a863
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/tal/tal.c:437 (del_tree) 0xaaaac030a94f
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/tal/tal.c:532 (tal_free) 0xaaaac030af77
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/io/io.c:496 (io_close) 0xaaaac02fc223
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ccan/ccan/io/poll.c:474 (io_loop) 0xaaaac02fe35b
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: lightningd/connect_control.c:451 (connectd_start_shutdown) 0xaaaac0212ccb
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: lightningd/lightningd.c:1506 (main) 0xaaaac022432b
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ../sysdeps/nptl/libc_start_call_main.h:58 (__libc_start_call_main) 0xffff84e87743
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: ../csu/libc-start.c:360 (__libc_start_main_impl) 0xffff84e87817
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0xaaaac01f2def
2025-12-04T04:55:07.883Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0xffffffffffffffff

[daywalker90]

The first logs don't reveal anything which is weird. The second logs just say that your bitcoin backend died, you should check bitcoind's logs on why that was. I have a suspicion that your OS is killing processes, maybe because it's running out of memory?

[PsySc0rpi0n]

The first logs don't reveal anything which is weird. The second logs just say that your bitcoin backend died, you should check bitcoind's logs on why that was. I have a suspicion that your OS is killing processes, maybe because it's running out of memory?

From Bitcoin Core logs, at the same time I can't see that Bitcoin Core has died:

2025-12-04T04:39:53Z [i2p] Creating transient SAM session bfd0b09772 with 127.0.0.1:7656
2025-12-04T04:39:53Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:39:53Z [i2p] Error connecting to qrjliqyrxrusbadgxq2qf4m7pm4iq2i5bod3gx6r3o6cdcrnyezq.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:42:59Z [i2p] Creating transient SAM session 73a4f432c1 with 127.0.0.1:7656
2025-12-04T04:42:59Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:42:59Z [i2p] Error connecting to 3jsg2mxfn4x6nmdwhjmoqjvgvfz5dyutolumxv3s6z5w3rzv6boa.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:49:53Z [i2p] Creating transient SAM session 3eea8b2c8a with 127.0.0.1:7656
2025-12-04T04:49:53Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:49:53Z [i2p] Error connecting to nijumgb33rivghpzy7h4mv3h7qgmq6ou37fjf7ow7nvgq6wp7t6a.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:51:06Z [i2p] Creating transient SAM session 594b3a8f80 with 127.0.0.1:7656
2025-12-04T04:51:06Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:51:06Z [i2p] Error connecting to 2xtjjuvzwjzkgoxaaxylxc3gqfakcgpblexz6fk7jwznhlg74agq.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:51:30Z [i2p] Creating transient SAM session 181b5888d0 with 127.0.0.1:7656
2025-12-04T04:51:30Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:51:30Z [i2p] Error connecting to wfkyqcudh5j47msnh62hice75r7n2hwbmiq57tuv2mc4bmdpogna.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:52:13Z Saw new header hash=00000000000000000000a6a058f0ef0d3c41c6450191e251d9e3cd0da98f1a9e height=926361
2025-12-04T04:52:13Z Saw new cmpctblock header hash=00000000000000000000a6a058f0ef0d3c41c6450191e251d9e3cd0da98f1a9e peer=11999
2025-12-04T04:52:15Z UpdateTip: new best=00000000000000000000a6a058f0ef0d3c41c6450191e251d9e3cd0da98f1a9e height=926361 version=0x20c96000 log2_work=95.970232 tx=1278979748 date='2025-12-04T04:51:50Z' progress=1.000000 cache=327.4MiB(2352484txo)
2025-12-04T04:53:43Z [i2p] Creating transient SAM session cd4d927356 with 127.0.0.1:7656
2025-12-04T04:53:43Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:53:43Z [i2p] Error connecting to zru3telkt7m5n5m3rcricucm3z5n4py7ixirmkjzifdixx434fka.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:53:59Z Saw new header hash=00000000000000000001aee57934949a2991fa372cea98f71a7e21c530870127 height=926362
2025-12-04T04:53:59Z UpdateTip: new best=00000000000000000001aee57934949a2991fa372cea98f71a7e21c530870127 height=926362 version=0x2006e000 log2_work=95.970244 tx=1278980002 date='2025-12-04T04:52:59Z' progress=1.000000 cache=327.4MiB(2352585txo)
2025-12-04T04:55:21Z [i2p] Creating transient SAM session 0de1c53819 with 127.0.0.1:7656
2025-12-04T04:55:21Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:55:21Z [i2p] Error connecting to cnfs2yrs5crxejk3fhwwogr2uagy5fhv2hmsudbzrvej7vgkbxsq.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:55:21Z [i2p] Creating transient SAM session c103a476d8 with 127.0.0.1:7656
2025-12-04T04:55:21Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:55:21Z [i2p] Error connecting to n56fod5echszkw6aykqminxc3o3nzorhzp5rjljs5rzulm7dnozq.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:56:58Z [i2p] Creating transient SAM session 0ed68096e9 with 127.0.0.1:7656
2025-12-04T04:56:58Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:56:58Z [i2p] Error connecting to tiogrc2irpoi5rqxc25juqu6pgghjyl3ezvbkf4ywbcvf3fwge5q.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:57:43Z [i2p] Creating transient SAM session 08dda82c9a with 127.0.0.1:7656
2025-12-04T04:57:43Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:57:43Z [i2p] Error connecting to r743osr67gpcypefzq2ohmt5n7o4rug4z7r57u5nz7t72m4winsa.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:57:45Z [i2p] Creating transient SAM session bb98f6038b with 127.0.0.1:7656
2025-12-04T04:57:45Z connect() to 127.0.0.1:7656 failed after wait: Connection refused (111)
2025-12-04T04:57:45Z [i2p] Error connecting to uc52rzz4xu5ikx6hl6r6sqxfmiyyxsffpcu5frrtepczidwjwuha.b32.i2p:0: Cannot connect to 127.0.0.1:7656
2025-12-04T04:59:03Z New block-relay-only v2 peer connected: version: 70016, blocks=926362, peer=12036
2025-12-04T05:01:33Z Saw new header hash=0000000000000000000058ab94be47676badeb3a845ea6aac9b8f5fc57c22454 height=926363
2025-12-04T05:01:37Z UpdateTip: new best=0000000000000000000058ab94be47676badeb3a845ea6aac9b8f5fc57c22454 height=926363 version=0x28000000 log2_work=95.970256 tx=1278983154 date='2025-12-04T05:01:13Z' progress=1.000000 cache=327.4MiB(2353103txo)

The memory issue you suggest may need some more investigation. I need check further!

[PsySc0rpi0n]

Ok, I think memory might be the cuprit of some of the issues. From what I can see, clnrest is kinda memory hungry, no?

$ smem -k -s pss -r | head -n 15
  PID User     Command                         Swap      USS      PSS      RSS 
 3824 psysc0rpi0n /home/psysc0rpi0n/Downloads   860.0K   735.9M   736.0M   737.5M 
 3778 psysc0rpi0n /home/psysc0rpi0n/Downloads    46.6M   418.3M   418.9M   422.2M 
 3804 psysc0rpi0n lightningd                    183.3M   290.0M   290.4M   294.2M 
 4180 psysc0rpi0n /home/psysc0rpi0n/Downloads     4.0K   128.1M   140.0M   158.9M 
 4178 psysc0rpi0n /home/psysc0rpi0n/Downloads     4.0K    88.4M   100.6M   121.2M 
 3858 psysc0rpi0n /home/psysc0rpi0n/Downloads   136.0K    96.3M    96.3M    97.8M 
 4213 psysc0rpi0n node rtl.js                    56.0K    76.9M    77.2M    79.9M 
 3810 psysc0rpi0n /home/psysc0rpi0n/Downloads    28.0K    53.5M    59.9M    89.7M 
 4175 psysc0rpi0n uv run lnbits                      0    30.5M    30.6M    32.1M 
 3818 psysc0rpi0n /home/psysc0rpi0n/Downloads    36.0K    14.3M    22.1M    56.3M 
 3821 psysc0rpi0n /home/psysc0rpi0n/Downloads    32.0K    11.0M    18.9M    53.0M 
 3819 psysc0rpi0n /home/psysc0rpi0n/Downloads    44.0K     8.9M    16.7M    50.9M 
 3816 psysc0rpi0n /home/psysc0rpi0n/Downloads    36.0K     7.1M    15.0M    49.1M 
 3899 psysc0rpi0n /home/psysc0rpi0n/Downloads        0    10.4M    13.4M    29.3M

$ cat /proc/3824/cmdline
/home/psysc0rpi0n/Downloads/lightning-v25.09/plugins/clnrest

Why it consumes so much memory? A single plugin... I it expected?

[daywalker90]

I'm no expert and i have recently tried to figure out how much memory a process on linux actually uses and my conclusion was: it's hard to tell. I thought it's just RSS but i got conflicting information saying that malloc is not aggressive enough to reclaim RSS, so it could stay high but be actual free memory. Anyways it should only get that high if you do a massive request through clnrest, like doing listforwards with i think hundres of thousands to millions of forwards in a response.

[daywalker90]

But in case there were actual memory shortages malloc would of course take any memory from other processes if it's free. So if you see your processes getting killed with oom errors and clnrest is still that high it should confirm something is wrong.

[PsySc0rpi0n]

From what I can see, and I'm no expert either, but with Gemini help, clnrest, bitcoind and lightningd are consuming most of it:

My node is quite small and not many routings are happening and also I'm only using RTL and LNbits. And LNbits is me testing the frontend. Nothing with too many action for my node.

[ShahanaFarooqui]

When I tested my small node on amd64 using::

printf "%-12s %-8s %-8s %-8s %-8s %-8s\n" "PROGRAM" "PID" "SWAP" "USS" "PSS" "RSS"
smem -k -c "pid swap uss pss rss" -s pss -r |
awk 'NR>1' |  # skip smem header
while read pid swap uss pss rss; do
    if lsof -nP -i | grep LISTEN | awk -v p="$pid" '$2==p' | grep -q .; then
        pname=$(lsof -nP -i | grep LISTEN | awk -v p="$pid" '$2==p {print $1}' | head -n 1)
        printf "%-12s %-8s %-8s %-8s %-8s %-8s\n" \
            "$pname" "$pid" "$swap" "$uss" "$pss" "$rss"
    fi
done

I received very reasonable numbers (PID 47159 is RTL & 237200 is cln-application):

PROGRAM      PID      SWAP     USS      PSS      RSS     
bitcoind     254112   0        53.6M    53.7M    56.3M   
node         47159    0        41.7M    50.5M    89.8M   
node         237200   0        40.7M    47.3M    84.3M   
prometheu    254361   0        24.7M    25.9M    35.6M   
cln-grpc     254300   0        19.9M    19.9M    21.8M   
clnrest      254301   0        18.2M    18.2M    20.4M   
wss-proxy    254304   0        12.6M    12.6M    14.9M   
lightning    254387   0        1020.0K  1.0M     3.1M    

According to AI - the much higher Swap, USS, PSS, and RSS values on ARMv7 are expected due to a combination of hardware and workload differences, whereas the smaller numbers on amd64 reflect headless, memory-efficient server processes.

Hardware architecture differences

• 32-bit processes can use more memory for the same workload because some memory allocations are less efficient.
• Many ARMv7 devices (e.g., Raspberry Pi) have limited RAM (1–4 GB), causing higher swap usage.

Why numbers are higher on ARMv7

• Processes like /home/.../Downloads (electron apps) load multiple library copies.
• Electron-based GUI apps often consume hundreds of MB even for small windows, inflating USS/PSS/RSS.

@daywalker90 Can clnrest be further optimised for ARMv7 without impacting performance on other architectures?