Mac OS Catalina Kernal Panic w/AD Guard v2.0.6.559 release

[Abdul Hadi Abo-Issa]

Hello,

Since I upgraded to Mac OS Catalina AD Guard is causing my Mac to Kernal Panic. If I quit it and don't let it run then I have no issues.

When I run the following command in terminal to find out why my Mac shut down I get the following:

log show --predicate 'eventMessage contains "Previous shutdown cause"' --last 24h


Filtering the log data using "composedMessage CONTAINS "Previous shutdown cause""

Skipping info and debug messages, pass --info and/or --debug to include.

Timestamp Thread Type Activity PID TTL

2019-07-17 22:27:55.958323-0400 0xdf Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: -62

-62 Watchdog timer detected unresponsive application, restarting the system.

I've attached a copy of the crash log.

Looking forward to hearing back.

 

[Chinaski]

Hello!

Please clarify. Does the situation repeat after reboot?
Try to reproduce the situation on Nightly version.

 

[Abdul Hadi Abo-Issa]

Hello Chinaski,

This happens even after rebooting. I just installed the nightly v2.1.0.572 nightly and will update you if it continues on happening.

-Abdul

 

[Abdul Hadi Abo-Issa]

Hello Chinaski,

The kernel panics continue on happening with 2.1.0.572 nightly.

Looking forward to hearing back.

-Abdul

 

[Abdul Hadi Abo-Issa]

2019-07-18 19:09:45 adguard-tcpkill - Crash (19 times)
Executable: /Library/Application Support/com.adguard.mac.adguard/*/adguard-tcpkill
Details:
dyld2 mode
abort() called
adguard-tcpkill(592,0x105c99d40) malloc: *** error for object 0x7f8708
006800: pointer being freed was not allocated

 

[Chinaski]

@Abdul Hadi Abo-Issa
Hello again!
Could you write the specified command in the terminal :

cd /Library/Application\ Support/com.adguard.mac.adguard/kext/
./adguard-tcpkill

Please send a screenshot with the result.

 

[Abdul Hadi Abo-Issa]

banksy@Banksys-Mac-Pro kext % cd /Library/Application\ Support/com.adguard.mac.adguard/kext/

banksy@Banksys-Mac-Pro kext % ./adguard-tcpkill

Version: 4

Usage: tcpkill [-p PID]... [-i interface] [-t TIMEOUT]

 

[prado]

Hi, I am also using on Catalina 10.15 Beta (19A512f).
I never had any kernel panics, but my logs are full of the same "malloc" error. (I am posting a picture here to contribute)

AdGuard version is the same 2.0.6.559 release (CL-1.4.13)

The error is un-noticed during usage, it happens in background, and the application is working very well. I just know this by the console logs (pictures attached)

It tells it is a basic malloc error, trying to free a pointer that was not allocated (perhaps was freed before and it is trying to free the pointer again)

All errors listed on the attached image contains the same error situation (marked on the picture)
The full log is also TXT attached here

my adguard-tcpkill version:

./adguard-tcpkill
Version: 3
Usage: tcpkill [-p PID]... [-i interface] [-t TIMEOUT]

 

[prado]

banksy@Banksys-Mac-Pro kext % cd /Library/Application\ Support/com.adguard.mac.adguard/kext/

banksy@Banksys-Mac-Pro kext % ./adguard-tcpkill

Hi Abdul Hadi Abo-Issa,
I inspected your PDF report and the kernel panic is very probably being caused by the Paragon NTFS kernel extension.

3rd party kernel extensions:
com.paragon-software.filesystems.ntfs

Try removing it or disable it, and verify if the kernel panic problem persists or not.