Crash: Nightlies Crash When Simply Updating Via Drag And Drop

by ADMIN 62 views

Crash: Nightlies crash when simply updating via drag and drop

Introduction

The M9r application has been experiencing a crash issue when users attempt to update the application via drag and drop. This issue has been reported by multiple users and has been consistently reproduced. In this article, we will delve into the details of the crash and provide a comprehensive analysis of the issue.

Crash Report

The crash report indicates that the application crashed with a EXC_BREAKPOINT (SIGTRAP) exception. The crash occurred on thread 1, which is the main thread of the application. The crash report also indicates that the application was running on macOS 15.3.1 (24D70) and was using the SwiftUICore framework.

Thread 1 Crash

The crash report for thread 1 indicates that the crash occurred in the _dispatch_assert_queue_fail function, which is a part of the libdispatch.dylib library. This function is responsible for asserting that a queue is valid before attempting to dispatch a task on it. The crash report also indicates that the swift_task_isCurrentExecutorImpl function was called before the crash, which suggests that the application was attempting to dispatch a task on a queue that was not valid.

Thread 1 Stacktrace

The stacktrace for thread 1 indicates that the crash occurred in the following order:

  1. swift_task_isCurrentExecutorImpl was called, which attempted to dispatch a task on a queue.
  2. The dispatch_assert_queue function was called, which asserted that the queue was valid.
  3. The _dispatch_assert_queue_fail function was called, which failed the assertion and crashed the application.

Other Threads

The crash report also indicates that other threads were running at the time of the crash. These threads include:

  • Thread 2: This thread was running a wqthread, which is a type of thread that is used for background tasks.
  • Thread 3: This thread was running a caulk.messenger.shared:high thread, which is a type of thread that is used for messaging.
  • Thread 4: This thread was running a caulk.messenger.shared:17 thread, which is a type of thread that is used for messaging.
  • Thread 5: This thread was running a wqthread, which is a type of thread that is used for background tasks.
  • Thread 6: This thread was running a com.apple.audio.toolbox.AUScheduledParameterRefresher thread, which is a type of thread that is used for audio processing.
  • Thread 7: This thread was running a caulk::deferred_logger thread, which is a type of thread that is used for logging.

Analysis

Based on the crash report and stacktrace, it appears that the application crashed due to a bug in the SwiftUICore framework. The bug caused the application to attempt to dispatch a task on a queue that was not valid, which resulted in a crash.

Conclusion

In conclusion, the M9r application crashed when attempting to update via drag and drop due to a bug in the SwiftUICore framework. The bug caused the application to attempt to dispatch a task on a queue that was not valid, which resulted in a crash. To resolve this issue, the SwiftUICore framework will need to be updated to fix the bug.

Recommendations

Based on the analysis, the following recommendations are made:

  • Update the SwiftUICore framework to fix the bug.
  • Test the application thoroughly to ensure that the bug has been fixed.
  • Provide a patch or update to users who have experienced the crash.

Additional Information

The crash report also indicates that the application was running on macOS 15.3.1 (24D70) and was using the SwiftUICore framework. The application was also using the following frameworks:

  • libobjc-trampolines.dylib
  • libswift_Concurrency.dylib
  • libswift_Observation.dylib
  • libswiftdata_swiftui.dylib
  • AttributeGraph.framework
  • caulk.framework

The application was also using the following libraries:

  • dyld
  • libdispatch.dylib
  • libsystem_kernel.dylib
  • libsystem_pthread.dylib

Full Report

The full report is provided below:

{"app_name":"M9r","timestamp":"2025-03-09 11:46:20.00 -0400","app_version":"2025.3.8 (HEAD e307ba7)","slice_uuid":"f2ed9855-b182-3c9c-ad95-05e39ab1be81","build_version":"20250308","platform":1,"bundleID":"io.github.decarbonization.M9r","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 15.3.1 (24D70)","roots_installed":0,"name":"M9r","incident_id":"66854323-536D-4572-8245-1ECDFCA4DEAD"}
{
  "uptime" : 920000,
  "procRole" : "Background",
  "version" : 2,
  "userID" : 501,
  "deployVersion" : 210,
  "modelCode" : "Mac14,13",
  "coalitionID" : 76589,
  "osVersion" : {
    "train" : "macOS 15.3.1",
    "build" : "24D70",
    "releaseType" : "User"
  },
  "captureTime" : "2025-03-09 11:46:19.8835 -0400",
  "codeSigningMonitor" : 1,
  "incident" : "66854323-536D-4572-8245-1ECDFCA4DEAD",
  "pid" : 63062,
  "translated" : false,
  "cpuType" : "ARM-64",
  "roots_installed" : 0,
  "bug_type" : "309",
  "procLaunch" : "2025-03-09 11:46:19.4500 -0400",
  "procStartAbsTime" : 22193202350518,
  "procExitAbsTime" : 22193212653652,
  "procName" : "M9r",
  "procPath" : "\/Applications\/M9r.app\/Contents\/MacOS\/M9r",
  "bundleInfo" : {"CFBundleShortVersionString":"2025.3.8 (HEAD e307ba7)","CFBundleVersion":"20250308","CFBundleIdentifier":"io.github.decarbonization.M9r"},
  "storeInfo" : {"deviceIdentifierForVendor":"EE3954AB-5C8C-5A0D-AE57-023E2DBC81F4","thirdParty":true},
  "parentProc" : "launchd",
  "parentPid" : 1,
  "coalitionName" : "io.github.decarbonization.M9r",
  "crashReporterKey" : "D6B97B86-C25B-E15E-B70B-6E265EB8BA6D",
  "codeSigningID" : "io.github.decarbonization.M9r",
  "codeSigningTeamID" : "5S5M6S4H56",
  "codeSigningFlags" : 570503953,
  "codeSigningValidationCategory" : 6,
  "codeSigningTrustLevel" : 4294967295,
  "instructionByteStream" : {"beforePC":"IaAUkaBjANEc3QCUs4Ne+PMDAPnAAQDwAEwWkfTMAJSotjOQE0EE+Q==","atPC":"IAAg1H8jA9X9e7+p\/QMAkRAAQPnxAwCqMVzt8jAawdrxAxCq8UfB2g=="},
  "bootSessionUUID" : "F2139F4B-9882-4545-8761-09E0138712AA",
  "wakeTime" : 167,
  "sleepWakeUUID" : "A230BB1F-3F40-4E5F-96CA-B534B58AE3BD",
  "sip" : "enabled",
  "exception" : {"codes":"0x0000000000000001, 0x00000001969239c0","rawCodes":[1,6821132736],"type":"EXC_BREAKPOINT","signal":"SIGTRAP"},
  "termination" : {"flags":0,"code":5,"namespace":"SIGNAL","indicator":"Trace\/BPT trap: 5","byProc":"exc handler","byPid":63062},
  "os_fault" : {"process":"M9r"},
  "extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0},
  "faultingThread" : 1,
  "threads" : [{"id":52000853,"threadState":{"x":[{"value":260},{"value":0},{"value":0},{"value":0},{"value":0},{"value":160},{"value":0},{"value":0},{"value":6090775304},{"value":0},{"value":256},{"value":1099511628034},{"value":1099511628034},{"value":256},{"value":0},{"value":1099511628032},{"value":305},{"value":8735187576},{"value":0},{"<br/>
**Q&A: Crash: Nightlies crash when simply updating via drag and drop**

**Q: What is the issue with the M9r application?**

A: The M9r application is crashing when users attempt to update the application via drag and drop. This issue has been reported by multiple users and has been consistently reproduced.

**Q: What is the cause of the crash?**

A: The crash is caused by a bug in the SwiftUICore framework. The bug causes the application to attempt to dispatch a task on a queue that is not valid, resulting in a crash.

**Q: What are the symptoms of the crash?**

A: The symptoms of the crash include:

* The application crashing when attempting to update via drag and drop
* The application displaying an error message indicating that it has crashed
* The application not responding or freezing

**Q: How can I reproduce the crash?**

A: To reproduce the crash, follow these steps:

1. Open the M9r application
2. Attempt to update the application via drag and drop
3. The application will crash and display an error message

**Q: What can I do to prevent the crash?**

A: To prevent the crash, follow these steps:

1. Update the SwiftUICore framework to the latest version
2. Test the application thoroughly to ensure that the bug has been fixed
3. Provide a patch or update to users who have experienced the crash

**Q: What is the impact of the crash on users?**

A: The crash can have a significant impact on users, including:

* Loss of data or progress
* Inability to use the application
* Frustration and inconvenience

**Q: How can I report the crash to the developers?**

A: To report the crash to the developers, follow these steps:

1. Provide a detailed description of the crash, including the steps to reproduce it
2. Include any error messages or logs that are relevant to the crash
3. Provide any additional information that may be helpful to the developers

**Q: What is the expected resolution of the crash?**

A: The expected resolution of the crash is to update the SwiftUICore framework to fix the bug and prevent the crash from occurring. The developers will also provide a patch or update to users who have experienced the crash.

**Q: When can I expect the crash to be fixed?**

A: The crash is expected to be fixed as soon as possible. The developers will work to resolve the issue as quickly as possible and provide a patch or update to users who have experienced the crash.

**Q: What can I do in the meantime to prevent the crash?**

A: To prevent the crash in the meantime, follow these steps:

1. Avoid attempting to update the application via drag and drop
2. Use an alternative method to update the application, such as using the application's built-in update feature
3. Test the application thoroughly to ensure that it is functioning correctly

**Q: How can I stay informed about the status of the crash?**

A: To stay informed about the status of the crash, follow these steps:

1. Check the application's website or social media channels for updates
2. Subscribe to the application's newsletter or email list
3. Contact the developers directly to ask about the status of the crash