Builder: crash (SIGSEGV) when closing the window, after Log/Delete/metal-bond attempts
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
Start by building the same commit with debug symbols so frames 1-5 of the SIGSEGV backtrace resolve to names, then read the close-window handler at builder+0x32ceb3 in the event table. Check whether the Log pane (the active wxLog target) or objects left by the failed Delete and metal-bond commands are used after they are destroyed. Done means exact reproduction steps are written down and the dangling pointer is identified and fixed, with the crash no longer occurring on close.
Written by the indexing model from the issue text.
Description
Seen: 2026-10-14 15:14, Debian 13, GNOME on Wayland, a test build of main + #322 (9.1.0 version string). The Builder crashed with SIGSEGV while its window was being closed; the ecce session in the terminal ended with "Segmentation fault (core dumped)". Earlier in that Builder session: selecting a line in the Log panel, Edit → Select Molecule, Delete attempts (#324), then closing the Log panel; metal–π bond attempts that failed (#325).
Core (systemd-coredump, PID 78624): the faulting instruction address is inside the Builder's own mapping but not executable code (kernel: segfault at 560212142b38 ip 560212142b38 ... error 15), i.e. a call through a corrupt or dangling pointer. Stack, with the package binary (stripped, so the Builder frames have no names):
#0 builder+0xf09b38 <- jump target, not code
#1 builder+0xae87a3
#2 builder+0x32aef0
#3 builder+0x32c50e
#4 builder+0x32ccf4
#5 builder+0x32ceb3 <- Builder's close-window handler (event table)
#6 wxEvtHandler::ProcessEventIfMatchesId
...
#12 wxWindowBase::Close(bool)
#13.. GTK delete-event (window manager close)
Next: exact steps to reproduce; then resolve frames 1–5 with a build of the same commit that keeps symbols. Candidates to check: something the close path touches after a pane was closed (the Log pane is also the active wxLog target), and objects left behind by the failed bond commands.
- Dominant language
- C
- Stars
- 10
- Forks
- 8
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FriendsofECCE/ECCE
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
FriendsofECCE/ECCE#353 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FriendsofECCE/ECCE#336 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
FriendsofECCE/ECCE#355 ·
-
Icons in MacOSOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 18/100
FriendsofECCE/ECCE#354 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
FriendsofECCE/ECCE#351 ·
All issues in FriendsofECCE/ECCE
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FujiNetWIFI/fujinet-lib#186 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100