Announcement

Collapse
No announcement yet.

macOS: FoxitPDFReaderUpdateService consumes unacceptable amount of CPU

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

  • #16
    Thank you for sharing it.

    Comment


    • #17
      What a disappointment to see that the problem is still not solved in version 11.1 of Foxit PDF Editor for Mac!

      I begin to believe that the Foxit Editor for Mac programmers are not as competent as they should be. Perhaps Foxit need to outsource that issue such that someone with proper programming skills can solve this silly problem (I am not aware of a single Mac software company with such an issue). This is more than embarrassing for Foxit. My university was about to switch from Adobe to Foxit – but as CIO I have decided it’s not going to happen based on the current experience with the obviously low skills of the programmers of Foxit for Mac.

      Foxit: Do something about it and let me know. My patience is basically used up.

      Comment


      • #18
        Axel Buchner
        Junior Member
        Axel Buchner We are very sorry for the trouble. Right when you reported this issue to us, it has reported to QA team immediately, they were able to reproduce this issue and confirm this is a bug, and pushed our R&D team to fix this issue for you quickly. We already pushing our internal team to raise the priority of this issue.
        I will keep an eye on this case and once there’s any update from R&D and QA, I will let you know asap.

        Comment


        • #19
          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.

          Comment


          • #20
            MacBildung
            Junior Member
            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.

            Comment


            • #21
              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

              Comment


              • #22
                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.

                Comment


                • #23
                  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

                  Comment


                  • #24
                    [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.

                    Comment

                    Working...
                    X