CHIRP

ENVIRONMENT: Mac Mini 2012 vintage, OS 10.7.5. I've frozen this as a stable version of the OS, and don't update.

OPERATION and SYMPTOMS: I've been using CHIRP for several years with no problem. I have two Baofeng UV-5R V2+ radios and both work fine with the interface cable---never any problems with this.

My last successful CHIRP download was the 20201008 daily version. I probably didn't use CHIRP until into the new year, but whenever I've downloaded any version later than 20201008, it terminates immediately with "Application quit unexpectedly". I'll try now to include the report generated by the OS. Further info is included AFTER the report:

Process: bash [21368]
Path: /Applications/CHIRP-daily-20210110.app/Contents/MacOS/chirp
Identifier: com.danplanet.chirp
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [301]

Date/Time: 2021-04-30 22:34:41.672 -0700
OS Version: Mac OS X 10.7.5 (11G63b)
Report Version: 9

Interval Since Last Report: 22394339 sec
Crashes Since Last Report: -184
Per-App Crashes Since Last Report: 3
Anonymous UUID: E57D3BC3-569D-4641-9354-1BB6A11ADB41

Crashed Thread: Unknown

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5fc01028

Backtrace not available

Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028
Logical CPU: 1

Binary images description not available

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 18898
thread_create: 0
thread_set_state: 0

Model: Macmini5,1, BootROM MM51.0077.B10, 2 processors, Intel Core i5, 2.3 GHz, 8 GB, SMC 1.76f0
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x859B, 0x435435313236344243313333392E4D313646
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x859B, 0x435435313236344243313333392E4D313646
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE4), Broadcom BCM43xx 1.0 (5.106.198.19.22)
Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: USB2.1 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0610, 0xfa120000 / 4
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0610, 0xfa121000 / 7
USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc52f, 0xfa121100 / 8
USB Device: Unicomp R7_2_Mac_10x_Kbrd_v7_47, 0x17f6 (Unicomp, Inc), 0x0864, 0xfa130000 / 6
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8281, 0xfa113000 / 5
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: BUP Slim SL, 0x0bc2 (Seagate LLC), 0xab24, 0xfd130000 / 5
USB Device: MacBook Air SuperDrive, apple_vendor_id, 0x1500, 0xfd120000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
************END OF REPORT ***************

To summarize, my experience with CHIRP was totally wonderful until I tried using a version later than 20201008. The termination is immediate---no bringing up of the CHIRP home screen, just bang and the above report.

My practice is to change the name of any downloaded CHIRP version to include its date, and to retain some older versions just in case the problem reported above happens.

I continue to use 20201008 with no problems. Once again, I've made no changes to the OS. If I've caused thia problem myself, please tell me what I did wrong (or failed to do right) and accept my apology for taking up your time.