Bug 495247 - kdiff3 crashes with segfault on macOS starting with 1.11 when comparing some files or directories
Summary: kdiff3 crashes with segfault on macOS starting with 1.11 when comparing some ...
Status: REPORTED
Alias: None
Product: kdiff3
Classification: Applications
Component: application (show other bugs)
Version: 1.11.4
Platform: macOS (DMG) macOS
: NOR crash
Target Milestone: ---
Assignee: michael
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-23 15:38 UTC by James O'Cull
Modified: 2025-01-16 21:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Crash report from macOS (79.07 KB, text/plain)
2024-10-23 15:38 UTC, James O'Cull
Details

Note You need to log in before you can comment on or make changes to this bug.
Description James O'Cull 2024-10-23 15:38:51 UTC
Created attachment 175149 [details]
Crash report from macOS

SUMMARY

Starting with 1.11 (any version) on both x86 (emulated) and arm64 (native) the application is crashing _some of the time_. It crashes consistently when I try to compare xml files.

It is working properly with x86 version on Rosetta on `kdiff3-1.10.7-macos-x86_64` (the application reports 1.10.6 though)

STEPS TO REPRODUCE
1. Install any version of 1.11.x
2. Try to diff an XML file
3. Observe crash

OBSERVED RESULT
Segmentation fault. Trace is below.

EXPECTED RESULT
Not crashing :)

SOFTWARE/OS VERSIONS
macOS: Sonoma 14.7

ADDITIONAL INFORMATION
Crash report is attached
Comment 1 michael 2024-12-22 21:36:00 UTC
Are we still having this issue with !.12.0?
Comment 2 Bug Janitor Service 2025-01-06 03:47:31 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 James O'Cull 2025-01-16 20:48:28 UTC
(In reply to michael from comment #1)
> Are we still having this issue with !.12.0?

I can reproduce this bug with the arm64 version of 1.12.0 but not with the x64_64 version (running under Rosetta)
Comment 4 michael 2025-01-16 21:19:08 UTC
If you still seeing TextDecoder::toUnicode then that means the wrong version some how got put up for Arm. TextDecoder::toUnicode is no longer in the source for master or 1.20. It was a temporary hold over for Qt5 as Qt6 initially did not support non-unicode encodings at all. In that case should be fixed next release cycle.