Announcement

Collapse
No announcement yet.

macOS: FoxitPDFReaderUpdateService consumes unacceptable amount of CPU

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Roy_Chen
    replied
    koken
    Please accept our deepest apology for the delay in responding.
    Regarding the situation you encountered, I may have to collect some information then forward it to our develop team.
    1. Are you currently using the Admin Console tool to receive/manage license keys? It's an important tool that must prepare for the AC system.
    2. Please upload your device information
    3. Uninstall Foxit program to see if this service disappeared, then reinstall Foxit and take a screenshot of FoxitPDFEditorUpdateService in the Activity Monitor. That would be good if you run Adobe(or other apps) at the same time so we can do a comparison.
    Appreciate it.

    Leave a comment:


  • koken
    replied
    Roy_Chen

    Hello Roy,
    What do you mean that the issue is fixed in version 11.1.1?
    I encountered the same issue after I deleted the FoxitPDF few months ago. I didn't notice it until this morning that the FoxitPDFReaderUpdateService had been consuming about 15% of CPU at background. I installed the latest version 11.1.2 this morning, but the FoxitPDFReaderUpdateService is still there even after I closed the software.

    In addition, I tried both of the suggestions below. They just did not work. I could not find Foxit Software in Application Support folder, neither could I get anything after I Input /Library/Application Support/Foxit Software/FoxitService.

    Could you please let me know what to do next now? I hereby attach the printscreen of my Mac. Click image for larger version

Name:	Screen Shot 2022-06-28 at 07.35.53.png
Views:	45
Size:	120.3 KB
ID:	189239


    For those who want to stop the wasting of battery capacity by FoxitPDFEditorUpdateService or FoxitPDFEditorUpdateService or both, here is a workaround until the Foxit developers solve this problem:
    1. On macOS 11, go to your global Library folder (typically: Macintosh HD/Library, this is not the Library folder in your user directory but rather the library folder in which things are stored that affect all users of your computer).
    2. In your Library folder, go to a folder called Application Support
    3. Find the folder Foxit Software which contains a folder called FoxitService which contains the file FoxitPDFEditorUpdateService or FoxitPDFEditorUpdateService or both; these are the apps that seem to cause the problem.
    4. Delete the folder called Foxit Software (i.e., Macintosh HD/Library/Application Support/Foxit Software).
    5. I am not sure whether you need to empty your trash but I did it.
    6. Restart. This solved the problem for me.



    MacBildung
    We apologize for any difficulty using Foxit Software.
    Here is a workaround you can follow up to see if it works:
    1.Open Finder
    2.Tap Command+Shift+G to get into system directory
    3.Input /Library/Application Support/Foxit Software/FoxitService
    4.You will see two progress (attached 1), please rename that two progress
    5.Reboot your computer, then access to the same location you will find that those two can be deleted.
    Check here for that video.

    Leave a comment:


  • richell_huang
    replied
    Originally posted by pdwalker View Post
    I decided to try my luck again with 11.1.1.0126 on MacOSX.

    The FoxitPDFReaderUpdateService CPU hog problem is gone for me.
    Yes, it is fixed in the version 11.1.1, so it should be working fine now.

    Leave a comment:


  • pdwalker
    replied
    I decided to try my luck again with 11.1.1.0126 on MacOSX.

    The FoxitPDFReaderUpdateService CPU hog problem is gone for me.

    Leave a comment:


  • Lisa_lee
    replied
    Axel Buchner ,Yes,you are right. The issue mentioned in this forum thread has already been addressed in our most current released version 11.1.1 of Foxit PDF Editor for Mac.
    Any further questions or concerns,please contact us again at any time.

    Leave a comment:


  • Axel Buchner
    replied
    It appears that the Foxit macOS team has solved the problem in version 11.1.1.0119 of Foxit PDF Editor for macOS.

    FoxitPDFEditorUpdateService has been active during the past 24 hours and has consumed virtually no CPU capacity during this period (and Foxit PDF Editor seems to consume fewer resources as well compared to earlier versions).

    Thank you!

    Leave a comment:


  • richell_huang
    replied
    Thank you for your update.

    Leave a comment:


  • pdwalker
    replied
    Updated, rebooted, let the computer settle down and FoxitPDFEditorUpdateService is back to its old tricks. It's gone now and the problem is solved.

    Leave a comment:


  • pdwalker
    replied
    Jan 23 2022, Foxit PDF Reader for Mac 11.0.0.0510 - the update service is consuming about 18-19% of my cpu constantly. Updating to 11.1.0.0925 now to see if that fixes things. If not, I'll just have to remove the software entirely.

    Leave a comment:


  • cherry
    replied
    [email protected]

    Thanks for your feedback. I've forwarded your feedback to Internal Report ID#MACLNX-10568 for the Dev team and QA's processing reference as well. The isue was planned to be in Dev Cycle 11-12. We'll add the info here when there's further update. Thank you again for your kind understanding.

    Leave a comment:


  • bour@pdx.edu
    replied
    This is still a bug in Foxit PDF Editor for Mac v. 11.1.0925. FoxitPDFEditorUpdateService appears to run 100% of the time, and takes between 6% and 33% of my CPU. This is unacceptable that this bug has gone on for many versions now. PLEASE HAVE YOUR DEV TEAM FIX IT ASAP.

    The workarounds that have been posted are NOT a fix.

    Thanks,

    -joe

    Leave a comment:


  • Lisa_lee
    replied
    Originally posted by [email protected] View Post
    How to Avoid Rebooting the System:

    Roy Chen provided a formula for killing the errant processes. Roy's solution requires the renaming of two files and then deleting the system and then deleting the files.

    However, I found that once the files have been renamed, I could then kill the processes (FoxitPDFReaderUpdateService and FoxitPDFEditorUpdateService) in finder and then the problem goes away without a need to reboot the system

    FYI: when I first discovered this issue, each process was using 15% of the CPU capacity.

    John
    Thanks for sharing. if you don't want to reboot your computer after you have renamed FoxitPDFEditorUpdateService or FoxitPDFReaderUpdateService file,you could choose to directly terminate the process (FoxitPDFReaderUpdateService or FoxitPDFEditorUpdateService) in finder.The purpose of rebooting is also for killing the mentioned process.

    Any further questions or concerns,please contact us again at any time.

    Leave a comment:


  • john@gardenway.org
    replied
    How to Avoid Rebooting the System:

    Roy Chen provided a formula for killing the errant processes. Roy's solution requires the renaming of two files and then deleting the system and then deleting the files.

    However, I found that once the files have been renamed, I could then kill the processes (FoxitPDFReaderUpdateService and FoxitPDFEditorUpdateService) in finder and then the problem goes away without a need to reboot the system

    FYI: when I first discovered this issue, each process was using 15% of the CPU capacity.

    John

    Leave a comment:


  • cherry
    replied
    MacBildung

    Thanks for your feedback and I've forwarded your comments to the Product Team as well in order to get it prioritized. We'll keep watching on this issue and update here when the issue been fixed.

    Thank you again.

    Leave a comment:


  • MacBildung
    replied
    I just want to chime in and express my disappointment (and befuddlement) that this serious bug has still not been fixed after five months. In all software projects I have been involved in, an issue such as this one would have been classified as a release blocker and fixed as soon as possible.

    The bug would be pretty bad if it caused a constant 5% CPU load, but it is so much worse: The CPU leak just keeps growing and growing, turning the Mac into a jet engine until the system eventually becomes unresponsive.

    Tech-savvy uses will eventually discover this thread and the workaround described therein, but there will be many other users who'll just wonder why their Macs are performing so poorly after installing Foxit PDF Editor.

    I can't believe we not only have to instruct all of our Mac users again to do the clunky workaround to remove the FoxitPDFEditorUpdateService binary from their systems, but also explain to them that this issue still has not been fixed months later. The latter stings in particular, because we had reassured them that Foxit was not just a good solution for Windows but also for their Macs when we purchased it for the whole organization to replace Adobe Acrobat Pro.

    Please make sure that the next release will no longer be affected by this issue.

    Leave a comment:

Working...
X