|
02-15-2024, 07:42 PM | #1 |
Junior Member
Join Date: Feb 2024
Posts: 1
|
Repeated Segmentation Faults
Hi,
I'm running DisplayLink Manager 1.10.0 build 117 which I believe is the latest release at the time of this posting. Over the last week or so DisplayLink Manager has started crashing constantly. I'm not sure exactly when it started so I can't identify if there was an update to MacOS that might have revealed this issue. Below in brief, and attached in full, please find the error dump from the system console. Sorry for the zip file, your site doesn't allow uploads of large enough txt files to contain the error messages. FWIW, I'm using a Plugable display extender model USBC-6950PDZ. Please let me know if there's a stable build I can try instead. Thanks! Code:
------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: DisplayLinkUserAgent [59897] Path: /Applications/DisplayLink Manager.app/Contents/MacOS/DisplayLinkUserAgent Identifier: com.displaylink.DisplayLinkUserAgent Version: 1.10.0 (117) Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-02-15 12:11:39.3694 -0800 OS Version: macOS 14.2.1 (23C71) Report Version: 12 Anonymous UUID: 799ECFA2-2852-20E1-BF1F-6E26178E8877 Sleep/Wake UUID: 5F6D0B20-4558-4C86-ADB7-A22ED6BC3BA0 Time Awake Since Boot: 1100000 seconds Time Since Wake: 559 seconds System Integrity Protection: enabled Crashed Thread: 24 Dispatch queue: com.apple.NSXPCConnection.m-user.com.apple.replayd Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [59897] VM Region Info: 0 is not in any region. Bytes before following region: 4300619776 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 100564000-1009f8000 [ 4688K] r-x/r-x SM=COW ...LinkUserAgent ... |
02-16-2024, 11:02 AM | #2 | |
Super Moderator
Join Date: Jan 2015
Posts: 431
|
Quote:
If you have not already done so, I would suggest installing 1.9 in order to see if that changes the behavior. For your reference, a good way to start with a 'clean slate' before installing 1.9 would be to use the new macOS End-User Cleaner tool --> https://support.displaylink.com/know...tool-for-macos If reverting to 1.9 is not an option, I would suggest reporting the issue with 1.10 directly to DisplayLink by following the process outlined here --> https://support.displaylink.com/know...to-displaylink |
|
|
|