BUG: Another Crash

Don Awalt
Don Awalt Member Posts: 3,555 ✭✭✭

Attn @Matt Mattox , I just got another crash, here on 42.0 beta 1! Logs are attached below. I was actually not using Verbum at all, on my Mac it was in window as a full-screen app and I was in the main window using another app. It crashed right into closing the app.

MacOS caught the crash -

Process: Verbum [19772]
Path: /Applications/Verbum.app/Contents/MacOS/Verbum
Identifier: com.logos.desktop.verbum
Version: 42.0.0.0359 (4200.1.103)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2025-04-25 20:06:26.4742 -0400
OS Version: macOS 15.4.1 (24E263)
Report Version: 12
Anonymous UUID: 29F732FC-FE9C-4ED1-DAE0-8F52E54FEFEE

Sleep/Wake UUID: EFCC5329-7C99-4FCE-98C2-E703E8F3198C

Time Awake Since Boot: 210000 seconds
Time Since Wake: 3963 seconds

System Integrity Protection: enabled

Crashed Thread: 70 .NET Network Address Change

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000018fccc664

Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process: exc handler [19772]

Tagged:

Comments

  • Matt Mattox
    Matt Mattox Member, Community Manager, Logos Employee Posts: 1,039
    edited April 28

    window as a full-screen app and I was in the main window using another app. It crashed right into closing the app.


    Can you explain the repro here? I'm a little confused on the last sentence on what you were doing.


    I'm picturing a two monitor set up and Logos is in full screen on your secondary monitor while another application is on your main monitor but how or when the application crashed is where I'm a tad confused.