Hello, I recently installed, reinstalled, and reinstalled again my Webroot SecureAnywhere software on my MAC because it continues to crash or fail at downloading the web browser component. If I open the application it will crash within 5-10 seconds. The details are below:
I appreciate any help. Thanks.
Process: Webroot SecureAnywhere [3092]
Path: /Applications/Webroot SecureAnywhere.app/Contents/MacOS/Webroot SecureAnywhere
Identifier: com.webroot.Webroot-SecureAnywhere
Version: 8.0.7.78 (8.0.7.78)
Code Type: X86-64 (Native)
Parent Process: launchd [177]
Responsible: Webroot SecureAnywhere [3092]
User ID: 501
Date/Time: 2015-01-20 12:43:20.032 +0100
OS Version: Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: 72FEB060-743A-BBF7-9739-14117A5741E1
Crashed Thread: Unknown
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Backtrace not available
Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00000000b021d000 rcx: 0x00000000b021a4c8 rdx: 0x0000000000000000
rdi: 0x000000000000560f rsi: 0x0000000000000006 rbp: 0x00000000b021a4f0 rsp: 0x00000000b021a4c8
r8: 0x6e6f697470656378 r9: 0x00007fff8660f8d0 r10: 0x0000000008000000 r11: 0x0000000000000206
r12: 0x00000000b021a650 r13: 0x00000000b021ab68 r14: 0x0000000000000006 r15: 0x00000000b021a530
rip: 0x00007fff8c853866 rfl: 0x0000000000000206 cr2: 0x0000000005fa7000
Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133
Binary images description not available
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 1306
thread_create: 0
thread_set_state: 0
Model: MacBookAir6,2, BootROM MBA61.0099.B12, 2 processors, Intel Core i5, 1.3 GHz, 4 GB, SMC 2.13f9
Graphics: Intel HD Graphics 5000, Intel HD Graphics 5000, Built-In
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3230554638454455302D474E2D4620
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3230554638454455302D474E2D4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (6.30.223.154.65)
Bluetooth: Version 4.2.7f3 14616, 3 services, 15 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SD0128F, 121.33 GB
USB Device: Internal Memory Card Reader
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Cruzer Fit
Thunderbolt Bus: MacBook Air, Apple Inc., 23.6
Page 1 / 1
I have exactly the same problem. Webroot Secure Anywhere crashes as soon as I try to do a scan.
Process: Webroot SecureAnywhere [690]
Path: /Applications/Webroot SecureAnywhere.app/Contents/MacOS/Webroot SecureAnywhere
Identifier: com.webroot.Webroot-SecureAnywhere
Version: 8.0.7.78 (8.0.7.78)
Code Type: X86-64 (Native)
Parent Process: launchd [146]
Responsible: Webroot SecureAnywhere [690]
User ID: 501
Date/Time: 2015-01-20 23:15:44.977 +0100
OS Version: Mac OS X 10.9.5 (13F34)
Report Version: 11
Process: Webroot SecureAnywhere [690]
Path: /Applications/Webroot SecureAnywhere.app/Contents/MacOS/Webroot SecureAnywhere
Identifier: com.webroot.Webroot-SecureAnywhere
Version: 8.0.7.78 (8.0.7.78)
Code Type: X86-64 (Native)
Parent Process: launchd [146]
Responsible: Webroot SecureAnywhere [690]
User ID: 501
Date/Time: 2015-01-20 23:15:44.977 +0100
OS Version: Mac OS X 10.9.5 (13F34)
Report Version: 11
Any answers for you yet?
Hi Jifunkera / Hi mickehe
Welcome to the Community Forums.
Have either of you Opened a Support Ticket to let the Support Team know about this (you can include a link to this thread so as to save you having to copy/type all the details in again)?
If not then please do so ASAP as they are the best people to assist in this matter.
Regards, Baldrick
Welcome to the Community Forums.
Have either of you Opened a Support Ticket to let the Support Team know about this (you can include a link to this thread so as to save you having to copy/type all the details in again)?
If not then please do so ASAP as they are the best people to assist in this matter.
Regards, Baldrick
Even if they didn't - I did a few days ago.@ wrote:
....
Have either of you Opened a Support Ticket to let the Support Team know about this (you can include a link to this thread so as to save you having to copy/type all the details in again)?....
Having volunteered my Memory stats then WSA Support were suggesting insufficient RAM or permissions or HDD. None of which are plausible to me due to regular maintenance utilities I run! :(
However for comparison here's my 10.9.5 MEmory stats from Activity monitor:
Scan (ALL Mounted Disks)
Activity Monitor App Memory: 5.36GB
Physical Memory 8.00GB File Cache: 796.9MB
Memory Used: 7.99GB Wired Memory: 923.9MB
Virtual Memory: 9.48GB Compressed: 714.8MB
Swap Used: 0 bytes
From View Scan in Progress -
1.5Miilion Files scanned so far in 60minutes…..
This will be 308th scan…. since 8.0.7.78:241 update.
My older Macbook with 4GB hasn't experienced this issue so.....
I suspect a kernel/application incompatability with WSAC when scanning so I'm now checking this again on Yosemeti 10.10.2 test partition with particularl attention to user application resident memory footprints.
Hi Tony
Hope that you are keeping well?
Please keep us posted on what you get back in terms of a response on this...it should be interesting.
Regards
Baldrick
Hope that you are keeping well?
Please keep us posted on what you get back in terms of a response on this...it should be interesting.
Regards
Baldrick
Well curently WSA support have left me to continue testing myself:@ wrote:
....
Please keep us posted on what you get back in terms of a response on this...it should be interesting.
.......
"We do not have any other users reporting this issue so we have to try and find out what is different about this computer than other macs. "
Which is stating the bleeding obvious and a little stange since I posted on this thread with two other users ehibiting the same symptoms! :p
Presumably they haven't raised a support ticket then.... :(
Anyway I'm currently trying to identify any significant memory leaks and check this out on Yosemite and another Macbook (with even less RAM!) 😉 Could take me a while with my other committments so don't hold your breath. ;)
Hi Tony
OK, well then, let's ask the other two users if they would be prepared to open tickets on this and therefore support your efforts to get some traction re. finding the cause of and therefore a solution to this issue for all Mac users who might run into it in the future.
What do you say?
Regards, Baldrick
OK, well then, let's ask the other two users if they would be prepared to open tickets on this and therefore support your efforts to get some traction re. finding the cause of and therefore a solution to this issue for all Mac users who might run into it in the future.
What do you say?
Regards, Baldrick
Hi Solly - Can't fault the concept or your intent! ;)
However after 3 past decades as a horse owner / rider /eventer I have first hand experience of : "You can take a horse to the water but....." :p
Well more accurately depending on the scenario and meds you have to hand, so that old adage should be teempered with reality and thus not always the case! However at my age, life is far too short already for me to politely, repeatedly and patiently encourage any animal or person to do something they clearly are not willing to engage in! ;)
By all means have a go yourself please! I was an under achiever at dressage so more subtle approaches were/are clearly beyond my comprehension and abilities! ;)
Thanks.
However after 3 past decades as a horse owner / rider /eventer I have first hand experience of : "You can take a horse to the water but....."
By all means have a go yourself please! I was an under achiever at dressage so more subtle approaches were/are clearly beyond my comprehension and abilities! ;)
Thanks.
OK quick update on this:
Firstly WSAC 8.0.7.8 has been upgraded to 8.0.8.33
I've tested/ implemented a few more memory monitors to see if the usual memory leaks from eg Safari (with multiple tabs) are a contributory factor. I can recommend (free) Memory Clean from Apple App Store which also allows you to set a threshold to "auto clean" if Free Space falls below your configured minima (set mine to 500MB).
I might have identified a "Tor package" that WSA hasn't yet whitelisted (PUA's) that appeared to cause a previous WSA "deadlock" but not yet had time to retest on latest 8.33 WSAC version.
Apart from the scan stalling the other previous symptoms are WS/WF Daemons maxing CPU in Activity Monitor.
At this stage you effectively can't SHUTDOWN WSAC or the Mac but have to revert to pulling the power (or "sudo" killing processes via Terminal)
Watch this space.... ;)
EDIT: Not even a week later and now we're on 8.0.8.38 ! - a moving target that means re- starting any test from scratch again! :p
Current test methodology and results on previous 8.0.8.33 version:
1. Using MemoryClean utility to auto clean when Freeemeory drops below 750MB.
2. Had a couple of GUI crashes but no Scan hanging / WSDaemon NOT maxing CPU.
3. HAd a couple of PUA's quarantined bu (re)scans completed ok.
Today stressing the system with a "throttled" 60GB Time Machine backup (halway thru at time of posting), 3 PUA's quarantined and the Rescan running for 100min WITH NO files shown on GUI but 334 scans done!!! but Menubar icon showing ~500K files and incrementing!
Otherwise WSDaemon still ok......
Keep watching!
Firstly WSAC 8.0.7.8 has been upgraded to 8.0.8.33
I've tested/ implemented a few more memory monitors to see if the usual memory leaks from eg Safari (with multiple tabs) are a contributory factor. I can recommend (free) Memory Clean from Apple App Store which also allows you to set a threshold to "auto clean" if Free Space falls below your configured minima (set mine to 500MB).
I might have identified a "Tor package" that WSA hasn't yet whitelisted (PUA's) that appeared to cause a previous WSA "deadlock" but not yet had time to retest on latest 8.33 WSAC version.
Apart from the scan stalling the other previous symptoms are WS/WF Daemons maxing CPU in Activity Monitor.
At this stage you effectively can't SHUTDOWN WSAC or the Mac but have to revert to pulling the power (or "sudo" killing processes via Terminal)
Watch this space.... ;)
EDIT: Not even a week later and now we're on 8.0.8.38 ! - a moving target that means re- starting any test from scratch again! :p
Current test methodology and results on previous 8.0.8.33 version:
1. Using MemoryClean utility to auto clean when Freeemeory drops below 750MB.
2. Had a couple of GUI crashes but no Scan hanging / WSDaemon NOT maxing CPU.
3. HAd a couple of PUA's quarantined bu (re)scans completed ok.
Today stressing the system with a "throttled" 60GB Time Machine backup (halway thru at time of posting), 3 PUA's quarantined and the Rescan running for 100min WITH NO files shown on GUI but 334 scans done!!! but Menubar icon showing ~500K files and incrementing!
Otherwise WSDaemon still ok......
Keep watching!
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.