09:55:43 I have a testnet wallet with a few thousand mined blocks, and I can't sweep_all 09:55:54 It just gets stuck after asking for the password 09:56:17 monero-wallet-cli uses 15-20% CPU sporadically, and it's been going on for at least an hour 09:59:23 if there is any "throttling" code that is supposed to maintain privacy when connecting to a remote node, it should probably off when connecting to a local node 09:59:31 Ive always found ridiculously large sweep_all txs to fail 10:05:32 You can gdb in and "thread apply all bt". 10:05:42 (in the wallet) 10:05:57 perf top might also shed some light. 10:06:36 If the bt isn't interesting, some cont + ^C should eventually find an interesting trace if the wallet is busy doing stuff. 10:06:54 AFAIK there is no wallet throttling code. 10:07:21 If the bt shows the wallet in the RPC call, then bt the daemon. 10:07:45 I'll need to build it locally to get proper callstacks 10:07:51 Running with log level 3 or 4 will also give you a fair idea of where it is. 10:07:59 right now it's just sitting there doing nothing, and I can't even kill the process 10:08:22 I'll try to get callstacks in the evening, need to go now 10:08:31 That hints at possible runaway memory usage with the OS swapping all the time ? 10:09:00 1103608 146924 20052 S 0.0 0.2 1:10.35 monero-wallet-c 10:09:03 not so much memory 10:09:09 that system has 64 GB RAM 10:13:27 testnet blockchain is 7.4 GB only, so I don't see how anything could swap there 10:13:45 KiB Mem : 65383152 total, 12340728 free, 24026888 used, 29015536 buff/cache 10:14:42 I just mentioned this since unkillable means stuck for a long time in kernel space. Absent I/O with buggy hardware, it seemed like the next likely reason. 10:16:03 hmm, maybe 10:16:23 That server is lingering since 2016 and never been updated 13:06:09 u wanna share the seed or the wallet bin and see if it can work on diff hardware? 13:06:31 or just try dif hardware 13:19:34 I'll try it on my notebook. Need to sync testnet first. 13:19:49 The wallet has 5614 outputs right now :D 13:49:10 Looks like it works better on the notebook. At least I get consistent 100% of on CPU core used 13:49:51 and it generated 39 transactions after ~1.5 minutes, all good