fscxfenced - DeepGuard's background process eating too much RAM

66f2e490
66f2e490 Posts: 56 Contributor
edited September 2023 in Web Browsing

Good day,

noticed that after upgrading to SAFE 18.4, when the uptime of the computer is more than one day, fscxfenced uses about 1GB of memory.

Is this a normal memory usage or a memory leak? Thanks in advance.

Apple M1, macOS 13.0.1 (22A400), F-Secure SAFE 18.4 (47125)

Bildschirm­foto 2022-11-22 um 15.13.27.jpg


Like Awesome

Accepted Answer

  • Firmy
    Firmy Posts: 1,879 Community Manager
    edited February 2023 Answer ✓

    Hi @66f2e490 @bobbyw

    Thank you for your post.

    We are aware of this issue. The issue is fixed in the new version 19.0.

    Kindly update to the latest version.

    Thank you and stay safe.

    Firmy
    Community Manager | F-Secure Community
    🔐 Strengthening digital security through knowledge and collaboration
    🌐 Explore our User Guides | Knowledge Base for self-help resources
    💻 Empower yourself with Cybersecurity Insights and protect what matters
    📢 Help Shape Our New Homepage! Share your input in our design survey.

    2Like Awesome

Answers

  • bobbyw
    bobbyw Posts: 8 Explorer

    My Mac just updated to 18.4 last night. I noticed today fscxfenced is using 9.65 GB of ram.

    2019 Mac Pro, MacOS Ventura 13.0.1, F-Secure SAFE 18.4 (47125)

    Screenshot 2022-11-22 at 4.02.26 PM.png


    Like Awesome
  • bobbyw
    bobbyw Posts: 8 Explorer
    https://community.f-secure.com/en/discussion/comment/131155#Comment_131155

    fscxfenced regularly consumes 8+ gigs of memory on my Mac. I have to force quit it at least every other day. One time I caught it consuming 18 gigs of RAM after forgetting to kill it for a week.

    I hope F-Secure is making this fix a priority. This is a huge memory leak.

    As a note, I have both Intel and M1 Macs. This only appears to be a problem on my Intel Mac.

    Like Awesome
  • ArthurVal
    ArthurVal Posts: 261 F-Secure Product Expert

    Hey, @bobbyw!

    Thanks for the report. The root cause of this behaviour has been identified and addressed in our internal development time product versions. The fix will be included in the upcoming 19.0 release in February.

    Best regards, Arthur

    F-Secure Technology, Mac Team

    3Like Awesome
  • LordStrongback
    LordStrongback Posts: 1 New Member

    I am on version 22.4, and still having this issue... problem has been going on for some time now...

    Like Awesome
  • ArthurVal
    ArthurVal Posts: 261 F-Secure Product Expert

    Hi, @LordStrongback

    Are you using a corporate/enterprise product?

    The fix for the issue has been deployed to Total product with version 19.0.

    22.4 sounds like version of a corporate product which WithSecure is responsible for nowadays.

    I would suggest reporting such issues on the corresponding Community site https://community.withsecure.com/

    Best regards, Arthur

    F-Secure Technology, Mac Team

    1Like Awesome
This discussion has been closed.
Feedback on New Design

Categories