![]() The company also stated that this was only affecting a small minority of customers. We would like to reassure customers that we are in close contact with Apple for the purposes of diagnosing and fixing this issue. ![]() We believe that this can only be an issue with Apple’s code and not our own, as we don’t ship any code that runs at the kernel level. What did ClamXAV say about this?Īt the time, the company issued the following statement to The Big Tech Question: However, Sentry is used to scan files in real-time – with this deactivated, you are relying on timed scans or performing them ad-hoc. It was found that turning off ClamXAV’s “Sentry” scanning resolved the problem. They can be identified by the screen going pink, followed by a sudden shut down and restart. This is what’s known as a “kernel panic”. Users running ClamXAV on M1 Macs were seeing occasional reboots, each of which reported an error similar to this: panic(cpu 4 caller 0xfffffe00184dd618): "uipc_send connected but no connection?" So what can you do now to prevent a ClamXAV crash on an M1 Mac? Find out below. A year on and things have changed, although the root cause is still to be fixed. At the time the cause wasn’t known, but there was a temporary workaround. Last year I reported that Macs running the new M1 chipset were crashing when running ClamXAV antivirus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |