I backported upstream test leak fixes (commits 294293ed, 9657fd3a, bbfd527d, fbeb86f8) to resolve the test suite SIGSEGV on stonking.
Both build-edit and build-tiny test suites pass cleanly with 2482/2482 assertions. Debian bug report: https://bugs.debian.org/1150796 Attaching debdiff for chr 0.1.81-1ubuntu1. ** Bug watch added: Debian Bug tracker #1150796 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1150796 ** Patch added: "chr_0.1.81-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/chr/+bug/2170633/+attachment/6008684/+files/chr_0.1.81-1ubuntu1.debdiff ** Also affects: chr (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1150796 Importance: Unknown Status: Unknown ** Description changed: chr 0.1.81-1 test suite fails on stonking with a SIGSEGV in SECTION("search") at src/tests/filetests.cpp:786. Cause: File instances allocated with new in test cases leak and stay active in the Qt event loop after the associated terminal is destroyed, causing a use-after-free crash in termpaint_text_measurement_feed_codepoint during cursorPositionChanged signal processing in later tests. Fix: Backport upstream test suite memory leak fixes (commits 294293ed, 9657fd3a, bbfd527d, and fbeb86f8) to manage File instances with std::unique_ptr or stack allocation across filetests.cpp, tests.cpp, and attributes.cpp. All 17 test cases pass (2482 assertions passed). + Debian Bug: https://bugs.debian.org/1150796 + --- [ Original Report ] chr 0.1.81-1 has been stuck in stonking-proposed for ~322 days; it fails to build on amd64, amd64v3, arm64, ppc64el and s390x (armhf/riscv64 aren't built): Build log (amd64): https://launchpad.net/ubuntu/+source/chr/0.1.81-1/+build/32793394 The build succeeds, but the test suite crashes: - actions - search - ../src/tests/filetests.cpp:786: FAILED: - {Unknown expression after the reported line} - due to a fatal error condition: - SIGSEGV - Segmentation violation signal - test cases: 12 | 11 passed | 1 failed - 1/1 editor:tests FAIL killed by signal 11 SIGSEGV + actions + search + ../src/tests/filetests.cpp:786: FAILED: + {Unknown expression after the reported line} + due to a fatal error condition: + SIGSEGV - Segmentation violation signal + test cases: 12 | 11 passed | 1 failed + 1/1 editor:tests FAIL killed by signal 11 SIGSEGV The crashing section is SECTION("search") in src/tests/filetests.cpp (~line 786): it sets a search text ("t"), then triggers F3 (find next) and waits for cursorPositionChanged. Debian: 0.1.81-1 builds and is in testing (no bugs). Differences in the stonking build environment that may matter: Qt 6.11.2+dfsg-4ubuntu2, KF6 SyntaxHighlighting 6.29.0-0ubuntu1 (Debian unstable has 6.30.0), and Ubuntu's default build flags (-O3 on ppc64el, LTO, _FORTIFY_SOURCE=3, frame pointers). Upstream: https://github.com/chr-editor/chr (active, last push 2026-09). ** Tags added: patch stonking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2170633 Title: chr FTBFS in stonking: editor test crashes (SIGSEGV) in search section To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chr/+bug/2170633/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
