F Secure Crashes everyday at the sames time

TAJ

I just installed from my IP Provider (Spectrum) there security suite by FSecure and I have a iMac with Macos Catilina 10.15.2  and now since I have installed it when I turn off my Computer off at night Fsecure crashes and generates Crash Report.  If I leave it on at or on sleep it does not do so!  Here is the crash report in a shorter version as not to exceed the character  limit  (Any help is appricated):

 

Process: F-Secure Mac Protection [10944]
Path: /Applications/Charter Security Suite/F-Secure Mac Protection.app/Contents/MacOS/F-Secure Mac Protection
Identifier: F-Secure Mac Protection
Version: 1.0.20591 (20591)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: F-Secure Mac Protection [10944]
User ID: 501

Date/Time: 2020-01-27 20:49:03.089 -0500
OS Version: Mac OS X 10.15.2 (19C57)
Report Version: 12
Anonymous UUID: 6FAB5B22-FC53-4153-9FE8-E94BA8353B9C

Time Awake Since Boot: 8700 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000003d98e9591c
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [10944]

VM Regions Near 0x3d98e9591c:
MALLOC_LARGE 00000001052b1000-00000001052c1000 [ 64K] rw-/rwx SM=PRV
-->
MALLOC_NANO 0000600000000000-0000600008000000 [128.0M] rw-/rwx SM=PRV

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff6d62baf0 object_isClass + 24
1 com.apple.Foundation 0x00007fff39b3e772 KVO_IS_RETAINING_ALL_OBSERVERS_OF_THIS_OBJECT_IF_IT_CRASHES_AN_OBSERVER_WAS_OVERRELEASED_OR_SMASHED + 50
2 com.apple.Foundation 0x00007fff39cdc1a1 NSKeyValueWillChangeWithPerThreadPendingNotifications.llvm.10384954629610297836 + 242
3 com.apple.Foundation 0x00007fff39b8c67f -[NSObject(NSKeyValueObserverNotification) willChange:valuesAtIndexes:forKey:] + 53
4 com.apple.AppKit 0x00007fff34f4c40d -[NSWorkspaceApplicationKVOHelper removeApplication:] + 246
5 com.apple.AppKit 0x00007fff34f4bfba applicationKVOHelperNotification + 97
6 com.apple.LaunchServices 0x00007fff38c32afc ___LSScheduleNotificationFunction_block_invoke_2 + 47
7 com.apple.CoreFoundation 0x00007fff374d67ab __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
8 com.apple.CoreFoundation 0x00007fff374d66ed __CFRunLoopDoBlocks + 379
9 com.apple.CoreFoundation 0x00007fff374d5731 __CFRunLoopRun + 1257
10 com.apple.CoreFoundation 0x00007fff374d4bd3 CFRunLoopRunSpecific + 499
11 com.apple.HIToolbox 0x00007fff3602b65d RunCurrentEventLoopInMode + 292
12 com.apple.HIToolbox 0x00007fff3602b2a9 ReceiveNextEventCommon + 356
13 com.apple.HIToolbox 0x00007fff3602b127 _BlockUntilNextEventMatchingListInModeWithFilter + 64
14 com.apple.AppKit 0x00007fff3469ceb4 _DPSNextEvent + 990
15 com.apple.AppKit 0x00007fff3469b690 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
16 com.apple.AppKit 0x00007fff3497f56a -[NSApplication _shouldTerminate] + 1364
17 com.apple.AppKit 0x00007fff34af39de -[NSApplication(NSAppleEventHandling) _handleAEQuit] + 323
18 com.apple.AppKit 0x00007fff346a2d5e -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 709
19 com.apple.Foundation 0x00007fff39b4c226 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 308
20 com.apple.Foundation 0x00007fff39b4c090 _NSAppleEventManagerGenericHandler + 98
21 com.apple.AE 0x00007fff38850092 0x7fff38843000 + 53394
22 com.apple.AE 0x00007fff3884f7b9 0x7fff38843000 + 51129
23 com.apple.AE 0x00007fff38847a27 aeProcessAppleEvent + 449
24 com.apple.HIToolbox 0x00007fff3603d2b8 AEProcessAppleEvent + 54
25 com.apple.AppKit 0x00007fff3469d15c _DPSNextEvent + 1670
26 com.apple.AppKit 0x00007fff3469b690 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
27 com.apple.AppKit 0x00007fff3468d3ae -[NSApplication run] + 658
28 com.apple.AppKit 0x00007fff3465f775 NSApplicationMain + 777
29 libdyld.dylib 0x00007fff6e9987fd start + 1

Thread 1:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff6ead925a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6ead95d0 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff374d6d0b __CFRunLoopServiceMachPort + 322
3 com.apple.CoreFoundation 0x00007fff374d58e7 __CFRunLoopRun + 1695
4 com.apple.CoreFoundation 0x00007fff374d4bd3 CFRunLoopRunSpecific + 499
5 com.apple.AppKit 0x00007fff3483fa72 _NSEventThread + 132
6 libsystem_pthread.dylib 0x00007fff6eb9ce65 _pthread_start + 148
7 libsystem_pthread.dylib 0x00007fff6eb9883b thread_start + 15

Thread 2:
0 libsystem_pthread.dylib 0x00007fff6eb98818 start_wqthread + 0

Thread 3:
0 libsystem_pthread.dylib 0x00007fff6eb98818 start_wqthread + 0

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000003d98e95900 rbx: 0x0000000000000000 rcx: 0x0000600002ae2a30 rdx: 0x00007ffeef3bc6e8
rdi: 0x00006000007e5900 rsi: 0x00007ffeef3bc6e0 rbp: 0x00007ffeef3bc6d0 rsp: 0x00007ffeef3bc698
r8: 0x0000000000000001 r9: 0x0000000000000002 r10: 0x00007fff90266ce0 r11: 0x00007fff37498e92
r12: 0x00006000007e5900 r13: 0x00007fff6d61dec0 r14: 0x0000000000000002 r15: 0x00007ffeef3bc6e0
rip: 0x00007fff6d62baf0 rfl: 0x0000000000010206 cr2: 0x0000003d98e9591c

Logical CPU: 1
Error Code: 0x00000004 (no mapping for user data write)
Trap Number: 14

 

Ukko

Hello,

 

Sorry for my reply. I am only an F-Secure user (their home solutions).

I think that it is good to try reach out Spectrum Support for assistance. You can to provide all information to them and they do able to investigate it.

An alternative option is to contact direct F-Secure Support Channels (for example, web-chat):

• https://www.f-secure.com/en/home/support/contact

But, most likely, it is not an option for branded solution. And it is supposed to contact Spectrum (and already they can to escalate it to F-Secure).

 

Thanks!

Cale

Hi,

 

We are going to roll out a maintenance release for the SAFE MAC 17.7 where this crash has been fixed. So if you still have a bit of patience, the crash will go away in a month or so. We are sorry for the inconvenience this is causing.

 

-Cale

TAJ

Thanks for Information about a maintance update for F-Secure!  Just wondering when it is released will it upgrade on it's own as part of the daily update? Or will I have to reinstall?

Cale

Hi,

 

Your ISP upgrade has been scheduled to the beginning of March. This upgrade requires you to manually run the installer (you will get a notification of it on your device).

 

This upgrade enables silent upgrades, which means that future product upgrades will be installed silently on the background.

 

-Cale

TAJ

Just wondering is there a timeline when this Maintenance Update is going to be released? Thought is would be by now!

Cale

Le' me check... we wanted to include few more fixes, so the update was postponed to week 15. Sorry about the delay.

-Cale

TAJ

The Maintenance Update that was released this week seems to have taken care of my problem Thanks