Please make sure that the next release will no longer be affected by this issue. 14.99/month This PDF editor is compatible with Mac OS X v10.9, Mac OS X v10.10, Mac OS X v10.11, or macOS v10.12. ![]() 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. Foxit Reader for Mac, as its name show, is the free PDF reader, but it also possesses editing features. 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. 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. 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. 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. I just want to chime in and express my disappointment (and befuddlement) that this serious bug has still not been fixed after five months.
0 Comments
Leave a Reply. |