Crashes on latest Catalina update on start

My Rekord Buddy Version: latest

My OS Version: latest

Steps required to reproduce the problem: start rekordbuddy

  1. List item

What I expected to happen: start

What actually happens instead: crashes immediately

Catalina Version : 10.15.1
Rekord buddy 2.1.4

Let me see if I can find the crash log for your issue. I’m running Catalina and I don’t see this on my end so it could be unrelated.

well happens to me on 3 different machines

Right. But I have way more than 3 user machines in the world where Catalina works fine so it could be something different with the config or the collection data itself.

Let me try and find the crash log and I’ll get back to you.

ok mate, hope you’ll find it

can I give you any additional info ? just to help to pin down the error ?

Process: Rekord Buddy 2 [1572]
Path: /Applications/Rekord Buddy 2.app/Contents/MacOS/Rekord Buddy 2
Identifier: audio.next.RekordBuddy2
Version: 2.1.4 (662)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Rekord Buddy 2 [1572]
User ID: 501

Date/Time: 2019-10-31 14:08:29.753 +0100
OS Version: Mac OS X 10.15.1 (19B88)
Report Version: 12
Bridge OS Version: 4.1 (17P1081)
Anonymous UUID: 1F8C3ACA-D422-B8C4-215F-F6D1CCED5694

Sleep/Wake UUID: C15E6CF9-83E9-4455-9CBC-AF5DB766FD4F

Time Awake Since Boot: 10000 seconds
Time Since Wake: 1300 seconds

System Integrity Protection: disabled

Crashed Thread: Unknown

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000b0
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1572]

Backtrace not available

Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x00000000f0598e98 rbx: 0x00000000f05967b0 rcx: 0x0000000000000000 rdx: 0x000000000015ae00
rdi: 0x00000000000000b0 rsi: 0x00000000f0500000 rbp: 0x000070000f285930 rsp: 0x000070000f285928
r8: 0x000000000f05963f r9: 0x000000000000003f r10: 0x00000000f0500000 r11: 0x00000000f0597660
r12: 0x00000000f1dd1b48 r13: 0x00000000f1dd1b70 r14: 0x0000600002e26398 r15: 0x0000000000000000
rip: 0x00007fff69b5038b rfl: 0x0000000000010202 cr2: 0x00000000000000b0

Logical CPU: 0
Error Code: 0x00000004 (no mapping for user data write)
Trap Number: 14

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: 7146
thread_create: 0
thread_set_state: 0

Model: MacBookPro15,1, BootROM 1037.40.124.0.0 (iBridge: 17.16.11081.0.0,0), 8 processors, 8-Core Intel Core i9, 2,4 GHz, 32 GB, SMC
Graphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin
Graphics: kHW_AMDRadeonPro560XItem, Radeon Pro 560X, spdisplays_pcie_device, 4 GB
Memory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2400 MHz, Micron, 16ATS2G64HZ-2G6B1
Memory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2400 MHz, Micron, 16ATS2G64HZ-2G6B1
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Oct 19 2019 15:33:10 version 9.113.2.0.32.5.39 FWID 01-5eb3e1fa
Bluetooth: Version 7.0.1f1, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: Apple T2 Bus
USB Device: Touch Bar Backlight
USB Device: Touch Bar Display
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Headset
USB Device: Ambient Light Sensor
USB Device: FaceTime HD Camera (Built-in)
USB Device: Apple T2 Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 47.3
Thunderbolt Bus: MacBook Pro, Apple Inc., 47.3

2.1.5 does crash too any news mate ?

2.1.6 Same Story mate

2.18 still crashing on start

Ok first, please don’t post multiple times. It doesn’t help anything or anyone.

I will post any update on this as soon as I get to it. I tackle issues in the order of importance (how many people are having the issue/problem).

In the meantime, keep on trying every new builds as they are posted. I often add info to try and isolate issues that I’m not seeing myself on my machines here. Thanks!

1 Like

alright but I don’t see the importance that way , I can not even start the program

2.10 crashes on start as well

It’s important because newer builds may have added information sent back to me when a problem occurs.

That’s how I can diagnose problems that only happen on other people’s machines.

I tweaked something that may affect your issue in 2.1.13. Can you give it a try?

If I’m correct, you should get a message asking you to reset your database.

it’s finally starting , I’ll give it a try in the evening

You never mentioned if you got the message asking you to reset your database.

Hi Damien, no didn’t pop up, is this a bad thing ?

Probably not what I thought it was then…