Open fiendish opened 5 years ago
A swift kick close to the metal Hack workaround:
Ask your operating system what it thinks the file-encoding is for the file meld is detecting incorrectly:
file badfile.txt
badfile.txt: data
file goodfile.txt
badfile.txt: ASCII text
file good_utf8file.txt
good_utf8file.txt: UTF-8
So the operating system is partly to blame for meld's error in file-encoding selection.
There is an XML key under /Applications/Meld.app/Contents/Resources/share/meld/org.gnome.meld.gschema.xml
named detect-encodings:
<key name="detect-encodings" type="as">
<default>[]</default>
...
</key>
I replaced the []
with ['UTF-8', 'latin1']
and then meld attempted to apply that file encoding rather than auto-detect the wrong one.
Another way is to fix your operating system and assert the encoding of the file either inside the file on the first line. When OSX can ascertain the correct file encoding, so too will meld.
@sentientmachine editation config didn't help
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: Meld [1967]
Path: /Applications/Meld.app/Contents/MacOS/Meld
Identifier: org.gnome.meld
Version: 3.21.0.osx3 (3.21.0.osx3)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 502
Date/Time: 2023-11-13 07:06:21.9216 +0100
OS Version: macOS 14.1 (23B74)
Report Version: 12
Bridge OS Version: 8.1 (21P1069)
Anonymous UUID: 267C4C3A-8578-9A10-40DF-0DD59BA811FD
Time Awake Since Boot: 800 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000040
Exception Codes: 0x0000000000000001, 0x0000000000000040
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1967]
VM Region Info: 0x40 is not in any region. Bytes before following region: 140737487466432
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
shared memory 7ffffff27000-7ffffff28000 [ 4K] r-x/r-x SM=SHM
Kernel Triage:
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 0x40 ???
1 libcairo.2.dylib 0x1049ee899 DataProviderReleaseCallback + 25
2 CoreGraphics 0x7ff817952bd1 data_release_info + 31
3 CoreGraphics 0x7ff81790ceab data_provider_finalize + 66
4 CoreGraphics 0x7ff8178d5ba4 data_provider_retain_count + 74
5 CoreFoundation 0x7ff811fd7e76 _CFRelease + 495
6 CoreGraphics 0x7ff8179322e9 image_finalize + 103
7 CoreFoundation 0x7ff811fd7da0 _CFRelease + 281
8 CoreGraphics 0x7ff817975d33 CG::DisplayListResourceImage::~DisplayListResourceImage() + 23
9 CoreGraphics 0x7ff817975d0a CG::DisplayListResourceImage::~DisplayListResourceImage() + 14
10 CoreGraphics 0x7ff817e2d0eb std::__1::shared_ptr
meld with no arguments produces
Segmentation fault: 11
So there's something going on with meld itself and not the arguments passed to it
@sentientmachine editation config didn't help Details
my problem was solved by the following mac os update
macOS 10.14.3 meld 3.19.2.osx6
If I click on any of the dropdowns (shown in image) in the status bar, meld exits and prints
Segmentation fault: 11
.The line/col dropdown additionally prints
/Applications/Meld.app/Contents/Resources/lib/python36.zip/meld/ui/statusbar.py:170: Warning: g_value_get_int: assertion 'G_VALUE_HOLDS_INT (value)' failed