Does anyone know what causes this crash?

Hey guys does anyone know what causes this crash?

Cubase 14-2025-01-25-230000.ips (225.8 KB)

I return to cubase after awhile and return to this crash, was just wondering what triggers it. happens often ; macbook m1 max

A description would help Apple users, instead of making them download and trawl through a crash dump.

The uploaded file contains a detailed crash log that includes exception information, faulting threads, and stack traces. Here’s a summary of the key findings:


Exception Details

  • Exception Type: EXC_BAD_ACCESS
  • Signal: SIGSEGV (Segmentation Fault)
  • Subtype: KERN_INVALID_ADDRESS at a particular memory address.

This indicates that Cubase attempted to access an invalid memory location, which may suggest a pointer authentication failure or memory corruption.


Faulting Thread

  • Thread ID: 68
  • Error: The main thread encountered an “Address size fault” during a call to [__NSCFArray objectAtIndex:].

This points to a possible issue with an array operation (e.g., accessing an index that doesn’t exist or a corrupted array).


Stack Trace

Key frames from the stack trace:

  1. -[__NSCFArray objectAtIndex:]
  2. CFArrayGetFirstIndexOfValue
  3. __CFRepositionTimerInMode
  4. __CFRunLoopDoTimer
  5. CFRunLoopRunSpecific
  6. -[NSApplication runModalForWindow:]

This sequence suggests that the crash occurred during an array operation, potentially within a timer callback in the Core Foundation run loop.


Possible Causes

  1. Plugin Issue: A VST or external plugin may have caused the invalid memory access.
  2. Cubase Bug: A bug in the Cubase application or its interaction with system libraries (like Core Foundation or Cocoa frameworks).
  3. Corrupt Project or Settings: A project file or preferences may contain corrupted data.
  4. System Configuration: Issues with macOS or hardware (e.g., memory errors or incompatibility with ARM architecture).

Recommended Steps

  1. Check Plugins:

    • Disable third-party VSTs and retry.
    • Update all plugins to their latest versions.
  2. Reset Preferences:

    • Backup and reset Cubase preferences to rule out corrupted settings.
  3. Update Software:

    • Ensure Cubase, macOS, and all plugins are fully updated.
  4. Reproduce the Issue:

    • Try to reproduce the crash with a specific project or action.
    • Check if the issue persists in a new project.
  5. Contact Steinberg Support:

    • Provide the crash log and details about your setup for further assistance.

Hi,

The crash is in the Universal Audio Oxide Tape. Please, get in touch with UAD.

Thread 68 Crashed:: Socket
0   uaudio_oxide_tape             	       0x3f464fda0 boost::asio::detail::timer_queue<boost::asio::time_traits<boost::posix_time::ptime>>::get_ready_timers(boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) + 144
1   uaudio_oxide_tape             	       0x3f4652e7c boost::asio::detail::kqueue_reactor::run(long, boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation>&) + 1712
2   uaudio_oxide_tape             	       0x3f4653abc boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&, boost::asio::detail::scheduler_thread_info&, boost::system::error_code const&) + 400
3   uaudio_oxide_tape             	       0x3f46537d0 boost::asio::detail::scheduler::run(boost::system::error_code&) + 196
4   uaudio_oxide_tape             	       0x3f4656d4c boost::asio::io_context::run() + 36
5   uaudio_oxide_tape             	       0x3f4656afc std::__1::__shared_ptr_emplace<UAThread, std::__1::allocator<UAThread>>::__on_zero_shared_weak() + 1060
6   uaudio_oxide_tape             	       0x3f46b52e8 UAThread::ThreadProcInternal() + 388
7   uaudio_oxide_tape             	       0x3f46b5b38 std::__1::thread::thread<void (UAThread::*)(), UAThread*, void>(void (UAThread::*&&)(), UAThread*&&) + 292
8   libsystem_pthread.dylib       	       0x197a3c2e4 _pthread_start + 136
9   libsystem_pthread.dylib       	       0x197a370fc thread_start + 8
2 Likes

Hi,

This is thread 0, not the CrashThread, therefore this is not relevant.

I agree, that it is not the crashthread.
It is relevant though as this sequence suggests that the crash occurred during an array operation with the key frame 1. -[__NSCFArray objectAtIndex:] and points to faulting thread 68 with the * Error: The main thread encountered an “Address size fault” during a call to [__NSCFArray objectAtIndex:].
Can surely be ignored if you go directly to thread with id 68 (CrashThread)