11.2 post-update crash report - CVMServer

[prwnr]

is anyone getting crash reports of CVMServer after update to Big Sur 11.2 today? (M1 Mac here)
I have around 10 such reports, tho I am not feeling anything crashing but its bugging me and I would prefer to clean up this thing.
any idea what can be causing this and if this is resolvable? or I rather have to wait till Apple will notice this and fix in next version?

Pasting the beggining of the crash report:

Process:               CVMServer [676]
Path:                  /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/CVMServer
Identifier:            CVMServer
Version:               177.22
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
Responsible:           CVMServer [676]
User ID:               0

Date/Time:             2021-02-02 21:46:03.550 +0100
OS Version:            macOS 11.2 (20D64)
Report Version:        12
Anonymous UUID:        0C416C47-0C23-3BC0-19E9-92E905A597C2


Time Awake Since Boot: 2400 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       KERN_PROTECTION_FAILURE at 0x00000001002b4000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Bus error: 10
Termination Reason:    Namespace SIGNAL, Code 0xa
Terminating Process:   exc handler [676]

 

[prwnr]

ok, I just figured out that it crashes every time Im starting any of a JetBrains IDEs. gotta try reporting to them and see if they know about this issue.

 

[k-hawinkler]

You could use EtreCheck to get to the bottom of this issue.

 

[jackson ja]

Seeing the same error on my M1 after 11.2 update. 5 automatic unattended reboots in a 12 hour period. Etrecheck has no definitive answer and suggests posting a question on the Apple community board.

Updated quickly in hopes of seeing a fix for the HDMI>DVI issue but still seeing the same problem (blank/flickering =unusable monitor).

 

[Coheebuzz]

Same here, my console is full of such errors and they all give EXC_BAD_ACCESS which seems to be a memory management error.

 

[Coheebuzz]

Just a tip, this error causes some apps to appear frozen when they are not, the picture on the monitor will freeze and you'll be navigating blindly but you can fix it by turning your monitor off and on rather than rebooting.

 

[prwnr]

Just a tip, this error causes some apps to appear frozen when then are not, the picture on the monitor will freeze and you'll be navigating blindly but you can fix it by turning your monitor off and on rather than rebooting.

for me there's actually no impact on the system nor the app that I can actually see. maybe there's a 0.1s freeze sometimes that I can spot. but other than that i'm just having a slam in crash reports

 

[Coheebuzz]

for me there's actually no impact on the system nor the app that I can actually see. maybe there's a 0.1s freeze sometimes that I can spot. but other than that i'm just having a slam in crash reports

It seems to be affecting some GPU-intensive apps the most, World of Warcraft is pretty much unusable since 11.2 and Cinema4D trial has been locking up constantly with the same error even while moving a simple cube around, and they are both native apps. Ironically all my Rosetta apps have been rock solid, zero crashes in over a month.

 

[lightway]

Hi everyone,

I actually just signed up for this post.

For me this entries happen on every start of Firefox (latest version 85.0.1 right now) since the 11.2 update. I also have a Intel MBP with exact the same software configuration at hand and can confirm it is only happening on my M1 MBA. If I disable the hardware acceleration in Firefox this error message is gone.

Haven't seen this error message with any other application yet. I also don't really notice any real problems except of the message. Maybe Firefox start a bit slower, but compared to my Intel MBP it is still faster.

I also want to relate the only other post I found on the Internet except of this one:

Game stuttering and crashing after upgrading to 11.2 on M1 Mac

The game was running beautifully before upgrading to 11.2 but since then it’s been running at what feels like 15fps even if the frame counter says otherwise, and sometimes locking up completely and forcing me to reboot. Also while the game is running my console becomes full of EXC_BAD_ACCESS...

eu.forums.blizzard.com

Seems to be related.

 

[Ritsuka]

CVMServer is a component of the OpenGL framework. WoW uses Metal, so it's probably completely unrelated.

 

[lightway]

Well in the WoW post the same error message is shown.
BTW: I found another application that is affected: This "Grapher" that even comes by default in Mac OS throws the same error into the log when letting it draw something.

I'm tempted to say that all OpenGL application on M1 Macs are affected since 11.2, but I'm still wondering that there are not many more reports about this. Even more so if popular applications like Firefox are affected. But maybe just no one notices, I also just noticed it while searching for something else.

 

[Coheebuzz]

Well in the WoW post the same error message is shown.
BTW: I found another application that is affected: This "Grapher" that even comes by default in Mac OS throws the same error into the log when letting it draw something.

I'm tempted to say that all OpenGL application on M1 Macs are affected since 11.2, but I'm still wondering that there are not many more reports about this. Even more so if popular applications like Firefox are affected. But maybe just no one notices, I also just noticed it while searching for something else.

No idea about OpenGL but the crashes in WoW seem to stop by enabling V-Sync and locking the refresh rate which will certainly help with pinpointing the root cause, most likely some timing issue.

 

[DAParsons]

Same crash, can't associate with anything specific. Happens often when I'm not active on the Mac (M1, 2020)

 

[Richard Tillard]

I have same crashes after clean install of 11.2 (MBP13, M1)

 

[dingamahoo]

I'm having the same problem--about 3-5 times a day now. Would love to find a solution. Luckily the M1 reboots so much faster than my old MBP.

 

[wiebe_w]

Same problem, several times a day.

After restart Big Sur reinstallation is suggested. After couple of hard resets, you can go on without reinstall.
Very annoying.

Have the slight feeling it has to do with HDMI, not sure.

 

[Richard Tillard]

Same problem, several times a day.
View attachment 1729057
After restart Big Sur reinstallation is suggested. After couple of hard resets, you can go on without reinstall.
Very annoying.

Have the slight feeling it has to do with HDMI, not sure.

I don't think it has anything to do with HDMI, because I don't use an external screen, but I still get the error from time to time. (11.2.1)

 

[wiebe_w]

I don't think it has anything to do with HDMI, because I don't use an external screen, but I still get the error from time to time. (11.2.1)

It could be it has to do with the USB-C connector. The crash report speaks about com.apple.driver.usb I connect my HDMI though the USB-C hub.

 

[Coheebuzz]

Check the crashed thread and frame, it's always this in my case....

0 libsystem_platform.dylib 0x000000019c6bd9cc _platform_memmove + 156

Which seems quite the generic error, not sure what we can pinpoint based on that, maybe the dev forum has something more to add.

 

[prwnr]

It could be it has to do with the USB-C connector. The crash report speaks about com.apple.driver.usb I connect my HDMI though the USB-C hub.

for me this crash report appears regardless of anything connected to the MacBook. so I personally wouldn't look there, unless this error affects such vast area that it happens in so many circumstances

 

[Macgnome]

I think its related to libdispatch.dylib which seems to related to CVMServer and I am seeing many errors in system.log

 

[zen77]

I just reinstalled OS; It still crashes on the CVM Server

Process: CVMServer [1054]
Path: /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/CVMServer
Identifier: CVMServer
Version: 177.22
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
Responsible: CVMServer [1054]
User ID: 0

Date/Time: 2021-02-21 13:39:58.980 -0800
OS Version: macOS 11.2.1 (20D75)
Report Version: 12


Time Awake Since Boot: 780 seconds
Time Since Wake: 130 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000104eb8000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Bus error: 10
Termination Reason: Namespace SIGNAL, Code 0xa
Terminating Process: exc handler [1054]

VM Regions Near 0x104eb8000:
MALLOC metadata 104eb4000-104eb8000 [ 16K] r--/rwx SM=PRV
--> VM_ALLOCATE 104eb8000-104ec8000 [ 64K] rwx/rwx SM=PRV
__TEXT 10514c000-1051c8000 [ 496K] r-x/r-x SM=COW /usr/lib/dyld

Application Specific Information:
dyld3 mode

Thread 0 Crashed:
0 libsystem_platform.dylib 0x00000001928559cc _platform_memmove + 156
1 CVMServer 0x0000000104e57364 cvmsServerElementBuild + 2920
2 CVMServer 0x0000000104e59904 __cvmsServInitializeConnection_block_invoke + 2372
3 libxpc.dylib 0x0000000192579958 _xpc_connection_call_event_handler + 164
4 libxpc.dylib 0x0000000192578460 _xpc_connection_mach_event + 960
5 libdispatch.dylib 0x00000001926614ec _dispatch_client_callout4 + 20
6 libdispatch.dylib 0x000000019267b610 _dispatch_mach_msg_invoke + 472
7 libdispatch.dylib 0x0000000192668648 _dispatch_lane_serial_drain + 272
8 libdispatch.dylib 0x000000019267c320 _dispatch_mach_invoke + 468

 

[zen77]

Bus Error (also known as SIGBUS and is usually signal 10) occur when a process is trying to access memory that the CPU cannot physically address.In other words the memory tried to access by the program is not a valid memory address.It caused due to alignment issues with the CPU (eg. trying to read a long from an address which isn’t a multiple of 4). SIGBUS is abbrivation for “Bus Error”.

SIGBUS signal occurs in below cases,
-> Program instructs the CPU to read or write a specific physical memory address which is not valid / Requested physical address is unrecognized by the whole computer system.
-> Unaligned access of memory (For example, if multi-byte accesses must be 16 bit-aligned, addresses (given in bytes) at 0, 2, 4, 6, and so on would be considered aligned and therefore accessible, while addresses 1, 3, 5, and so on would be considered unaligned.)

 

[zen77]

Can others confirm their crashes have this common theme?

Termination Signal: Bus error: 10
Termination Reason: Namespace SIGNAL, Code 0xa
Terminating Process: exc handler [1054]

 

[Macgnome]

As soon as I open Firefox (85.0.2 (64-bit) M1 version) I get CVMServer crash log


Termination Signal: Bus error: 10
Termination Reason: Namespace SIGNAL, Code 0xa
Terminating Process: exc handler [749]


I think its to do with libdispatch and xpc