Sudden Crash

Bug Reports
1

To help us respond to your bug report as efficiently as possible, please fill out the follow template (and delete all instructions)

Platform & OS Version

Platform: Mac
OS Version: 15.5
OS Language Setting: English

App Version

Version: Aeon Timeline
Version: 3.4.23
Shell Version: 3.4.23
Opening mode: about.editor
Operating System: Mac OS X 15.5.0
Device Model: Mac14,2

Problem Description + Screenshots

Provide a detailed description of the bug that you encountered. Please include any screenshots that are relevant.

Steps to reproduce

Provide step-by-step instructions to recreate the bug
it suddenly started to appear, whenever I open a specific file.
Answer the following questions, if possible:

  • Are you able to reproduce this bug reliably?
    Yes I can
  • Can you make this bug happen with a clean timeline file?
    Nope it does not happen
  • Does it only happen with a specific timeline file?
    yes

Any relevant files?

I also sent the file into suppport mail by email ongun@mac.com

2

Screenshot 2025-06-28 at 11.37.48
Screenshot 2025-06-28 at 11.37.483132×2040 429 KB

The crash report indicates that Aeon Timeline encountered a fatal error (SIGABRT) triggered by calling the system function abort(). Here is a detailed but simplified breakdown of the problem and recommendations:

:technologist:

Crash Analysis (Simplified)

1.

Crash Type:

  • Exception: SIGABRT (Abort Trap: 6)
  • Indicates the app explicitly terminated itself due to encountering an unrecoverable state.

2.

Location of Crash:

  • Thread 0 (com.apple.main-thread) crashed.
  • Function call stack:
libsystem_kernel.dylib      __pthread_kill + 8
libsystem_pthread.dylib     pthread_kill + 296
libsystem_c.dylib           abort + 124
libc++abi.dylib             abort_message + 132
libc++abi.dylib             std::__terminate(void (*)()) + 28
libc++abi.dylib             __cxa_rethrow + 188
libobjc.A.dylib             objc_exception_rethrow + 44
AppKit                      -[NSApplication run] + 552
AppKit                      NSApplicationMain + 880
dyld                        start + 6076

3.

Cause:

  • The crash occurred due to an unhandled Objective-C exception, which eventually triggered an abort() call by the runtime to terminate the app.
  • The root cause is not explicitly detailed, but common reasons include:
    • Memory corruption or invalid memory access
    • Assertion failures in the application’s logic
    • Unhandled runtime exceptions (e.g., data corruption, unexpected states)

:warning:

Likely Root Causes:

  • Corrupted or incompatible data file: Aeon Timeline might be loading a corrupted or very large timeline file, exceeding its handling capacity.
  • Internal logic error: Possible bug in Aeon Timeline’s code.
  • Third-party library issue (Sentry): The presence of Sentry (crash-reporting library) indicates it was attempting to catch and handle an internal exception.