Skip to content

Remotely triggered abort (SIGABRT, signal 6) crash with experimental-dual-fund enabled #8945

@whitslack

Description

@whitslack

I was experimenting with dual funding, but my node is unstable with experimental-dual-fund enabled. It crashed twice in less than a day, with the same questionably nonsensical stack trace:

2026-03-16T04:09:05.625Z **BROKEN** lightningd: FATAL SIGNAL 6 (version 25.09.3-gentoo-r0)
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: common/json_filter.c:130 (json_filter_new) 0x563e0038e0d0
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: common/json_filter.c:138 (json_filter_subobj) 0x563e0038e0d0
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x7fc4ff41c08f
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x7fc4ff4787e3
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x7fc4ff41bf61
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x7fc4ff3fff8e
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: lightningd/jsonrpc.c:63 (command_check_done) 0x563e002ee76c
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: lightningd/jsonrpc.c:59 (command_check_done) 0x563e002ee76c
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: lightningd/onchain_control.c:1459 (handle_onchaind_spend_htlc_success) 0x563e0032c2d2
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: lightningd/onchain_control.c:1682 (onchain_msg) 0x563e0032c2d2
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: lightningd/channel.c:747 (new_channel) 0x563e00300fdd
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: lightningd/datastore.c:192 (json_datastore) 0x563e0035961d
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x563e0041059a
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x563e00410898
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x563e00410938
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x563e00411072
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x563e003fe8c8
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: ./wallet/wallet.h:1454 (offer_status_active) 0x563e0035a614
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: lightningd/offer.c:600 (json_listinvoicerequests) 0x563e0035a614
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x563e003fe623
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x563e00400a4b
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: lightningd/jsonrpc.c:465 (json_add_help_command) 0x563e0032493e
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: lightningd/jsonrpc.c:528 (json_help) 0x563e0032493e
2026-03-16T04:09:05.626Z **BROKEN** lightningd: backtrace: /var/tmp/portage/sys-devel/gcc-15.2.1_p20260214/work/gcc-15-20260214/libgcc/../gcc/common/config/i386/cpuinfo.h:1063 (get_available_features) 0x563e002f78bc
2026-03-16T04:09:05.627Z **BROKEN** lightningd: backtrace: /var/tmp/portage/sys-devel/gcc-15.2.1_p20260214/work/gcc-15-20260214/libgcc/../gcc/common/config/i386/cpuinfo.h:1156 (cpu_indicator_init) 0x563e002f78bc
2026-03-16T04:09:05.627Z **BROKEN** lightningd: backtrace: /var/tmp/portage/sys-devel/gcc-15.2.1_p20260214/work/gcc-15-20260214/libgcc/config/i386/cpuinfo.c:62 (__cpu_indicator_init) 0x563e002f78bc
2026-03-16T04:09:05.627Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x7fc4ff402019
2026-03-16T04:09:05.627Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0x7fc4ff402135
2026-03-16T04:09:05.627Z **BROKEN** lightningd: backtrace: lightningd/anchorspend.c:125 (add_one_anchor) 0x563e002f9970
2026-03-16T04:09:05.627Z **BROKEN** lightningd: backtrace: lightningd/anchorspend.c:167 (create_anchor_details) 0x563e002f9970
2026-03-16T04:09:05.627Z **BROKEN** lightningd: backtrace: (null):0 ((null)) 0xffffffffffffffff

I've disabled dual funding again, as I can't risk my node crashing and being offline for hours before I notice, so unfortunately I will not be able to help in further diagnosing the issue.

I can say that I was not interacting with my node at the time of the crashes. They were remotely triggered, presumably by a peer that was attempting to initiate a dual-funded channel opening with my node.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions