[fixed] BDCoreIssues process, high CPU


On two of my Macs the BDCoreIssues process has started running almost continuously, consuming 95+% CPU per process, with apparently quite a lot of disk reads too.  This all seems to have started in the past week or so on both - was there some update that went out recently that could be causing this?


 

Comments


  • I am having the same issue. I did try to uninstall Bitdefender Antivirus for Mac (manually removed everything in /Library/Bitdefender after a reboot so that BDCoreIssues and related processes were gone. After which I reinstalled the software hoping this will resolve the problem but it's still hammering my CPU via BDLDaemon (44 to ~70% CPU) or BDCoreIssues (almost constantly at ~70%) for a very long time.


    I'm on mac OS 10.12.1 (16B2555), using Antivirus for Mac v5.1.0.8. Autopilot is on and I have an active yearly subscription.


  • More data on this:  It definitely seems to have started after the last restart-required Bitdefender update (I'm also on v5.1.0.8).  Additionally, there are thousands of these messages in the system console logged by BDCoreIssues


     


    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG 



  • 4 hours ago, mysteryclock said:



    More data on this:  It definitely seems to have started after the last restart-required Bitdefender update (I'm also on v5.1.0.8).  Additionally, there are thousands of these messages in the system console logged by BDCoreIssues


     


    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG 



    I can confirm the same:


    default 18:59:04.848940 +0200 BDCoreIssues CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG


     

    Screen Shot 2016-11-17 at 18.58.41.png


  • I did sample the process and checked the open descriptors:


    sudo lsof -p 202
    Password:
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    BDCoreIss 202 root cwd DIR 1,5 1156 2 /
    BDCoreIss 202 root txt REG 1,5 401728 9163969 /Library/Bitdefender/AVP/common.bundle/BDCoreIssues
    BDCoreIss 202 root txt REG 1,5 317168 9163972 /Library/Bitdefender/AVP/common.bundle/lib/libCommonTools.dylib
    BDCoreIss 202 root txt REG 1,5 52320 9163974 /Library/Bitdefender/AVP/common.bundle/lib/libIpc.dylib
    BDCoreIss 202 root txt REG 1,5 86360 9163973 /Library/Bitdefender/AVP/common.bundle/lib/libconnect.dylib
    BDCoreIss 202 root txt REG 1,5 236728 9163976 /Library/Bitdefender/AVP/common.bundle/lib/libpush.dylib
    BDCoreIss 202 root txt REG 1,5 32768 9236531 /private/var/db/mds/messages/se_SecurityMessages
    BDCoreIss 202 root txt REG 1,5 25909040 5121419 /usr/share/icu/icudt57l.dat
    BDCoreIss 202 root txt REG 1,5 1621284 9163608 /Library/Bitdefender/AVP/antivirus.bundle/bdnc/libbdnc.so
    BDCoreIss 202 root txt REG 1,5 393792 5125988 /System/Library/Frameworks/Security.framework/Versions/A/PlugIns/csparser.bundle/Contents/MacOS/csparser
    BDCoreIss 202 root txt REG 1,5 694528 5125776 /usr/lib/dyld
    BDCoreIss 202 root txt REG 1,5 650444800 9129194 /private/var/db/dyld/dyld_shared_cache_x86_64
    BDCoreIss 202 root 0r CHR 3,2 0t0 307 /dev/null
    BDCoreIss 202 root 1u CHR 3,2 0t0 307 /dev/null
    BDCoreIss 202 root 2u CHR 3,2 0t91 307 /dev/null
    BDCoreIss 202 root 3r DIR 1,5 238 412832 /Users/Shared
    BDCoreIss 202 root 4u KQUEUE count=0, state=0xa
    BDCoreIss 202 root 5 PIPE 0xded18855de0fba3d 16384 ->0xded18855de0fb97d
    BDCoreIss 202 root 6 PIPE 0xded18855de0fb97d 16384 ->0xded18855de0fba3d
    BDCoreIss 202 root 7 PIPE 0xded18855de0fb8bd 16384 ->0xded18855de0fd2fd
    BDCoreIss 202 root 8 PIPE 0xded18855de0fd2fd 16384 ->0xded18855de0fb8bd
    BDCoreIss 202 root 9 PIPE 0xded18855de0fd3bd 16384 ->0xded18855de0fb7fd
    BDCoreIss 202 root 10 PIPE 0xded18855de0fb7fd 16384 ->0xded18855de0fd3bd
    BDCoreIss 202 root 11 PIPE 0xded18855de0fd47d 16384 ->0xded18855de0fb73d
    BDCoreIss 202 root 12 PIPE 0xded18855de0fb73d 16384 ->0xded18855de0fd47d
    BDCoreIss 202 root 13u unix 0xded18855dd3e03b5 0t0 ->0xded18855dd3e2b8d
    BDCoreIss 202 root 14u unix 0xded18855dd3e2b8d 0t0 ->0xded18855dd3e03b5
    BDCoreIss 202 root 15u unix 0xded18855dd3e0095 0t0 ->0xded18855dd3e2c55
    BDCoreIss 202 root 16u unix 0xded18855dd3e2c55 0t0 ->0xded18855dd3e0095
    BDCoreIss 202 root 17u unix 0xded18855e09162f5 0t0 /var/tmp/Bitdefender/SocketI
    BDCoreIss 202 root 18u unix 0xded18855e0914545 0t0 /var/tmp/Bitdefender/SocketI
    BDCoreIss 202 root 19 NPOLICY
    BDCoreIss 202 root 20u IPv4 0xded18855eae4a645 0t0 TCP 192.168.8.104:51811->reverse-unset.bbu.exdc01.bitdefender.net:http (ESTABLISHED)
    BDCoreIss 202 root 21u systm 0t0
    BDCoreIss 202 root 22r DIR 1,5 35972 413596 /usr/bin
    BDCoreIss 202 root 26 PIPE 0xded18855e1f2e57d 16384 ->0xded18855e1f2e33d
    BDCoreIss 202 root 27 PIPE 0xded18855e1f2e33d 16384 ->0xded18855e1f2e57d
    BDCoreIss 202 root 28u KQUEUE count=0, state=0xa
    BDCoreIss 202 root 29 PIPE 0xded18855e1f2e63d 16384 ->0xded18855e1f2e27d
    BDCoreIss 202 root 30 PIPE 0xded18855e1f2e27d 16384 ->0xded18855e1f2e63d
    BDCoreIss 202 root 31 PIPE 0xded18855e1f2e1bd 16384 ->0xded18855e1f2e6fd
    BDCoreIss 202 root 32 PIPE 0xded18855e1f2e6fd 16384 ->0xded18855e1f2e1bd
    BDCoreIss 202 root 34r DIR 1,5 1156 2 /
    BDCoreIss 202 root 36u systm 0t0
    BDCoreIss 202 root 37u unix 0xded18855e0916ac5 0t0 ->0xded18855e0914095
    BDCoreIss 202 root 38u unix 0xded18855e0914095 0t0 ->0xded18855e0916ac5
    BDCoreIss 202 root 39u unix 0xded18855e09166dd 0t0 /var/tmp/Bitdefender/SocketI
    BDCoreIss 202 root 41 FSEVENT


    Activity monitor is also reporting a lot of process faults (see the attached screenshot)


     

    Screen Shot 2016-11-17 at 19.04.13.png


  • Hello,


     


    Please open a ticket with our support team using [email protected] as we need more information related to this issue, please follow the steps below to generate the required logs.


    1. Open the Bitdefender main window

    2. Press Command-Shift-D from your keyboard

    3. Click on Help from the menu bar and select Enable Debug Mode

    4. Restart your Mac, open the Activity Monitor and check the BDCoreIssues process

    5. If it starts using too much CPU, please wait for 5-10 minutes in order for Bitdefender to gather more information

    6. Send us a new BDProfiler log (it should automatically collect the new logs) How to use the BDProfiler

    7. Also send us a system log


    -go to Applications > Utilities

    -open Console

    -right-click on system.log on the left side and select Reveal in Finder

    -send us the system.log file from the folder that just opened along side the one from the BDProfiler


  • Hi there, I've gathered the data and sent it to the email provided. Let me know whether there's anything else I could do to help.


    Cheers,


    -- Attila


  • Hello,


     


    My colleagues from the support team will investigate and contact you via email with a solution and they will let you know if they need anything else to resolve this.



  • 2 hours ago, Sorin G. said:



    Hello,


     


    My colleagues from the support team will investigate and contact you via email with a solution and they will let you know if they need anything else to resolve this.



    If the support teams comes up with anything can you also chime in here with suggestions?

  • Chris Johnson
    edited November 2016


    I am having this issue on both my 2016 MacBook Pro 13" and 2015 MacBook Pro 13".  This process has been eating tons of CPU time on both computers.  This issue is so bad it is killing my laptops batteries and I have had to uninstall BitDefender.  Disabling AutoPilot does not idle the process out.  The console log is blasting hundreds of these non-stop.


     


    default    20:36:43.453960 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:43.454060 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:43.472178 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:43.472236 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:43.490366 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:43.490427 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:43.498962 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:43.499059 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:43.507381 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:43.507496 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.111113 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.111174 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.126567 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.126672 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.144526 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.144583 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.407672 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.407725 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.411889 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.411942 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.428353 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.428410 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.437189 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.437253 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.445429 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.445486 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.462996 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.463055 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.503088 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.504104 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.566326 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.566407 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.584618 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.584776 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.600540 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.600629 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.616556 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG

    default    20:36:44.616642 -0700    BDCoreIssues    CSSM Exception: -2147411889 CSSMERR_CL_UNKNOWN_TAG


     


  • I've got exactly the same problem on two Macs and I've logged a ticket too. It's now meant that Time Machine backups are never completed unless the product is uninstalled. This is the reason I moved away from another vendor to BD after the Sierra update as Sophos had a similar problem.


    As well as the CSSM Exception message, this is followed, and repeated by MacOS error: -67050 and trustd cert [2]: AnchorTrusted =(leaf)[force]>0 console errors here.


  • Same problem here.  It just started about 1-2 weeks ago.  I tried a complete uninstall and reinstall of BitDefender, and that did not help.  BDCoreIssues is killing the battery life on my MacBook Pro.  And the processor is running really hot.  Whatever BitDefender did with their last update, they need to get this fixed.


  • I have this problem too, the support agent knows nothing about it, and I can't use the directions above, when I hit COMMAND-SHIFT-D all I get is a sound, nothing else.  The BitDefender profiler tool does not accept a password. I'm stuck. and I need HELP! Will email Support, hope that helps.


  • Same problem, initially masked by a similar high CPU usage issue with MS Outlook and MS Word (since fixed by turning off "auto-detect language"). Now BDCoreIssues is consistently highest CPU process. Really looking forward to solution. 



  • 3 minutes ago, NauticalNeilP said:



    Same problem, initially masked by a similar high CPU usage issue with MS Outlook and MS Word (since fixed by turning off "auto-detect language"). Now BDCoreIssues is consistently highest CPU process. Really looking forward to solution. 



    Interesting, where are you turning off the auto-detect language setting for Office?



  • 4 minutes ago, Kmatt said:



    Interesting, where are you turning off the auto-detect language setting for Office?



    Same question - found it for Word, didn't find it for Outlook.  Or does it secretly propagate over there??



  • 1 minute ago, mysteryclock said:



    Same question - found it for Word, didn't find it for Outlook.  Or does it secretly propagate over there??



    Ah, found it for Outlook. Start a new email then Edit > Language > Language ...


  • Glad you found it.  For anyone else looking, here is the Microsoft community post that talks about the problem and solution.  http://answers.microsoft.com/en-us/msoffice/forum/msoffice_officeinsider-mso_mac/outlook-for-mac-1528-high-cpu-load/5ca4b1f1-e396-49b8-9aad-13467926b9b2?page=3 


  • Same issue here. Eagerly awaiting a fix.


  • Same here.


  • Same problem, ended up uninstalling until they fix this.


  • Hello all,


     


    We have identified the cause of the high CPU usage triggered by a recent update of Bitdefender Antivirus for Mac and our developers are currently working on a fix which will be delivered in a future product update. We will update this topic as soon as the fix is released. Also, those of you who contacted us via email will receive a reply from our representatives once the situation is addressed.


    Thank you all for your help and patience.

     


  • /index.php?/profile/34114-georgia/&do=hovercard" data-mentionid="34114" href="<___base_url___>/index.php?/profile/34114-georgia/" rel="">@Georgia thank you for the team's work identifying the issue, and for updating us all here in the thread.  We're looking forward to that fix!


  • /index.php?/profile/34114-georgia/&do=hovercard" data-mentionid="34114" href="<___base_url___>/index.php?/profile/34114-georgia/" rel="">@Georgia Thanks for the update.  While I recognize what is required to build a new release with such a fix, can you give us an approximate timeframe (few days, few weeks, or more than a month) on when this fix release will be available (or when you might release it to a few of us for beta testing purposes)?  


    Thanks in advance ....... Neil


  • Hi,


    Unfortunately an ETA is not available yet, but we will post back as soon as the fix is implemented by automatic update of Bitdefender Antivirus for Mac.

     


  • Same issue, although using up around 50-60% CPU. Given the thread above and no firm resolution ETA from Bitdefender, uninstalled AntiVirus for Mac, even though I've prepaid for a year. If this issue is not resolved soon, what a black mark for the company


  • Ditto. Same high CPU usage problem as reported by others. Thanks for a fix soon. BTW, love the product.


  • Same issue.  Posting so will be notified of update.  Please hurry!  :-)


  • Hello all,


     


    This issue is now fixed in the latest version 5.1.19, live for Bitdefender Antivirus for Mac.  Bring up Bitdefender and choose Actions on the menu bar > Update Virus Signature > click on Restart Now to finalize the update.


    Hope you have a nice week ahead!



  • Just now, Georgia said:



    Hello all,


     


    This issue is now fixed in the latest version 5.1.19, live for Bitdefender Antivirus for Mac.  Bring up Bitdefender and choose Actions on the menu bar > Update Virus Signature > click on Restart Now to finalize the update.


    Hope you have a nice week ahead!



    Thanks Georgia, I updated 20 minutes ago and it's working well for me. Time machine is back to normal as well as CPU usage. No sign of BDCoreIssues in Activity Monitor!


  • Glad to hear that everything is back to normal, Kmatt. Thank you for your confirmation.


    We now declare this topic closed.

This discussion has been closed.