Channels are not forgotten because "Owning subdaemon onchaind died"

I'm on v25.12.1

I have a handful of channels that

the status on the listpeerchannels showing "Owning subdaemon onchaind died (61952)".
Upon investigation, the lnlog contains events of:

>```
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: FATAL SIGNAL 11 (version v25.12.1-modded)
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: common/daemon.c:46 (send_backtrace) 0x5b686293d382
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: common/daemon.c:83 (crashdump) 0x5b686293d3d1
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 ((null)) 0x74456f04532f
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:999 (handle_htlc_onchain_fulfill) 0x5b6862929673
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:1262 (output_spent) 0x5b6862929bf5
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:1596 (handle_onchaind_spent) 0x5b6862929ea9
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:1643 (wait_for_resolved) 0x5b686292a59b
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:2467 (handle_our_unilateral) 0x5b686292bb96
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:3497 (main) 0x5b686292dc12
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: ../sysdeps/nptl/libc_start_call_main.h:58 (__libc_start_call_main) 0x74456f02a1c9
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: ../csu/libc-start.c:360 (__libc_start_main_impl) 0x74456f02a28a
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: (null):0 ((null)) 0x5b6862927654
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: (null):0 ((null)) 0xffffffffffffffff
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: FATAL SIGNAL (version v25.12.1-modded)
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: common/daemon.c:46 (send_backtrace) 0x5b686293d382
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: common/status.c:207 (status_failed) 0x5b68629418c2
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: common/subdaemon.c:18 (status_backtrace_exit) 0x5b6862941a00
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: common/daemon.c:87 (crashdump) 0x5b686293d3df
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0 ((null)) 0x74456f04532f
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:999 (handle_htlc_onchain_fulfill) 0x5b6862929673
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:1262 (output_spent) 0x5b6862929bf5
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:1596 (handle_onchaind_spent) 0x5b6862929ea9
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:1643 (wait_for_resolved) 0x5b686292a59b
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:2467 (handle_our_unilateral) 0x5b686292bb96
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: onchaind/onchaind.c:3497 (main) 0x5b686292dc12
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: ../sysdeps/nptl/libc_start_call_main.h:58 (__libc_start_call_main) 0x74456f02a1c9
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: ../csu/libc-start.c:360 (__libc_start_main_impl) 0x74456f02a28a
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: (null):0 ((null)) 0x5b6862927654
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: backtrace: (null):0 ((null)) 0xffffffffffffffff
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-onchaind-chan#23242: STATUS_FAIL_INTERNAL_ERROR: FATAL SIGNAL
>2026-03-20T09:15:49.911Z **BROKEN** 02xx-chan#23242: Owning subdaemon onchaind died (61952)
>```

and the STDERR shows:

>```
>lightning_onchaind: FATAL SIGNAL 11 (version v25.12.1-modded)
>0x5b686293d335 send_backtrace
> common/daemon.c:38
>0x5b686293d3d1 crashdump
> common/daemon.c:83
>0x74456f04532f ???
> ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
>0x5b6862929673 handle_htlc_onchain_fulfill
> onchaind/onchaind.c:999
>0x5b6862929bf5 output_spent
> onchaind/onchaind.c:1262
>0x5b6862929ea9 handle_onchaind_spent
> onchaind/onchaind.c:1596
>0x5b686292a59b wait_for_resolved
> onchaind/onchaind.c:1643
>0x5b686292bb96 handle_our_unilateral
> onchaind/onchaind.c:2467
>0x5b686292dc12 main
> onchaind/onchaind.c:3497
>0x74456f02a1c9 __libc_start_call_main
> ../sysdeps/nptl/libc_start_call_main.h:58
>0x74456f02a28a __libc_start_main_impl
> ../csu/libc-start.c:360
>0x5b6862927654 ???
> _start+0x24:0
>0xffffffffffffffff ???
> ???:0
>lightning_onchaind: FATAL SIGNAL (version v25.12.1-modded)
>0x5b686293d335 send_backtrace
> common/daemon.c:38
>0x5b68629418c2 status_failed
> common/status.c:207
>0x5b6862941a00 status_backtrace_exit
> common/subdaemon.c:18
>0x5b686293d3df crashdump
> common/daemon.c:87
>0x74456f04532f ???
> ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
>0x5b6862929673 handle_htlc_onchain_fulfill
> onchaind/onchaind.c:999
>0x5b6862929bf5 output_spent
> onchaind/onchaind.c:1262
>0x5b6862929ea9 handle_onchaind_spent
> onchaind/onchaind.c:1596
>0x5b686292a59b wait_for_resolved
> onchaind/onchaind.c:1643
>0x5b686292bb96 handle_our_unilateral
> onchaind/onchaind.c:2467
>0x5b686292dc12 main
> onchaind/onchaind.c:3497
>0x74456f02a1c9 __libc_start_call_main
> ../sysdeps/nptl/libc_start_call_main.h:58
>0x74456f02a28a __libc_start_main_impl
> ../csu/libc-start.c:360
>0x5b6862927654 ???
> _start+0x24:0
>0xffffffffffffffff ???
> ???:0
>```

and beyond the BROKEN lines there are these events happening:

>```
2026-03-20T09:15:26.019Z INFO 02xx-chan#23242: Restarting onchaind (ONCHAIN): closed in block 859196
2026-03-20T09:15:26.019Z UNUSUAL 02xx-chan#23242: Peer permanent failure in ONCHAIN: Funding transaction spent: onchain txid caxx (reason=unknown)
2026-03-20T09:15:26.019Z UNUSUAL 02xx-chan#23242: Not dropping our unilateral close onchain since we already saw caxx confirm.
2026-03-20T09:15:26.019Z INFO 02xx-chan#23242: State changed from ONCHAIN to FUNDING_SPEND_SEEN
2026-03-20T09:15:33.180Z INFO 02xx-chan#23242: State changed from FUNDING_SPEND_SEEN to ONCHAIN
2026-03-20T09:16:03.692Z INFO 02xx-chan#23242: RBF onchain txid c3xx (fee 134sat) with txid b0xx (fee 267sat)
>```

All funds appear to be recovered.

Also, I have to mention that, these are old channels that have been sitting zombied on my nodes prior before upgrading to "v25.12.1".