High cpu usage due to bsdtar process

Discussion in 'General Questions' started by CarlB7, Oct 9, 2019.

  1. CarlB7

    CarlB7 Bit Poster

    Messages:
    1
    Just upgraded to Mac OS X 10.15 (Catalina) and Parallels Version 15.0.0 (46967) and having a constantly running fan and major battery drain due to Mac process bsdtar. System is a 2016 13" MacBook Pro. What is bsdtar and why does it run long at 100% cpu usage?
     
  2. AnastasiosG

    AnastasiosG Bit Poster

    Messages:
    2
    Same problem with me
     
  3. AnastasiosG

    AnastasiosG Bit Poster

    Messages:
    2
    Does this has to do with this file ? Can we delete it to stop? Screenshot 2019-10-10 at 09.49.32.png
     
  4. JariH

    JariH

    Messages:
    1
    Same problem here.
     
  5. TomS27

    TomS27

    Messages:
    1
    Same issue with me
     
  6. SelvM

    SelvM Bit Poster

    Messages:
    1
    Also have the same issue, any suggestions how to solve it?
     
  7. Maria@Parallels

    Maria@Parallels Parallels Team

    Messages:
    3,893
  8. RichardF11

    RichardF11 Bit Poster

    Messages:
    1
    Same problem here.
    Thank you to the comments above. My workaround was to uninstall parallels toolbox as a I rarely use it. Not a fix.
    I am running parallels 14.1.3 and have not used it since installing catalina last week.
    The bsdtar process started this morning out of the blue, eventually freezing the machine. A couple of restarts and the process proliferated.
     
    iuliann likes this.
  9. JimC3

    JimC3 Bit Poster

    Messages:
    2
    I also have the same problems.
    Running Parallels 15.0.0 and MacOS Catalina 10.15. bsdtar takes around 100% CPU. Windows Task Manager shows very little CPU consumed. I updated Parallels Toolbox (again), to no effect. Quitting Parallels Toolbox also had no effect.
     
  10. iuliann

    iuliann

    Messages:
    1
    Thank you for this "workaround"!
     
  11. JimC3

    JimC3 Bit Poster

    Messages:
    2
    The MacOS Catalina 10.15 Supplemental update seems to have eliminated this problem for me.
     

Share This Page