Announcement

Announcement Module
Collapse
No announcement yet.

Reader not closing task manager process when pdf is closed

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bug Reader not closing task manager process when pdf is closed

    In Vista x64, Reader 5.3.1 sometimes opens a 2nd reader process in task manager. I can't reproduce this - consistently - when or why it opens another instance of reader. I'm certainly not intentionally launching another instance from a shortcut, them opening a file in the 2nd instance. But periodically, I look in task mgr for something else & there are the 2 separate Foxit processes, both using approx. same memory (depending on files opened).

    When it DOES have 2 instances in task manager, it often shows path to the open file, for one of the instances, under task manager "Command Line" column.
    When this happens, there doesn't appear to be 2 reader UI's open on desktop. But, if I close one of the files (from Foxit UI) the separate process for the file (shown in Task Manager) keeps running long after the file is closed. There's also the process listed separately for the reader application itself, AND the other instance, showing actual path to file, under task mgr's Command Line column when this happens.

    Not sure if it's a bug or special circumstance causing a 2nd, separate Foxit instance to show in task mgr. If Foxit opens a separate process in Windows when a pdf is opened (that process uses a good bit of resources), then it should close the process fairly quickly, after the open file is closed in Foxit.

    The only ways I'm opening pdf's is in Foxit are - File > Open;
    from Explorer - R click a pdf >Open (Foxit is default reader);
    or R click file in Explorer & use Open With (again, Foxit is there, listed as default app);
    From an email attachment - R click>Open (Foxit is default reader set in Thunderbird). I'm NOT using Foxit plugin for Thunderbird.

    I'm fairly sure it shouldn't open 2nd Foxit instance, unless I launched it a 2nd time. Not sure it'd even allow that. Any suggestions?
    Thanks.

  • #2
    It works fine with Foxit Reader 5.3.1 on my side, Would you mind making some screenshots of the task manager Process so i could forward to our QA team for a closer look?
    BTW, have you tried to reinstall it to see if it helps?Sometimes, reinstallation may fix some unknown problem.

    Comment


    • #3
      Thanks. No, haven't tried the standard "have you tried reinstalling it" yet. As said, it's hard for me to reproduce, but I've seen it more than a couple times. If happens again, I'll post screens & maybe even Process Explorer screens.
      NOTE: Don't have Adobe reader on this box. Not particularly a fan.

      Re: reinstalling. I have to say, I can't think of any other software (esp. stable vers., NOR most beta software) that I have had to uninstall / reinstall as MANY times as Foxit reader, to fix problems. Probably had to do it 6 times in last 5 - 6 yrs (that's between versions). I don't "upgrade" - I uninstall / reinstall new versions, so theoretically, should have FEWER problems.

      Yes, reinstalling sometimes fixes problems, but leads to the question: Why does Foxit Reader get corrupted or screw up more than any software I use? And I'm a pretty advanced computer user / trouble shooter. In fact, it's VERY rare I have to reinstall any apps to solve problems.

      I've had this box w/ Vista hm prem x64 (pre installed) since 2009. I've never had to reinstall Windows, nor had any major problems - like having to run Windows Repair util. So, what's up w/ Foxit?

      Not being rude, but spouse has both Foxit & Adobe reader. I can't recall - since 2007 - ever having to uninstall / reinstall Adobe - to fix a problem. On spouse's machine, Adobe doesn't develop any problems / get corrupted.
      I don't like some of Adobe Corp's philosophy, but now I'm seeing Foxit reader taking about same CPU / RAM resources as Adobe - on same machine, same file, same time. Unless I'm the ONLY one seeing that, Foxit has definitely lost some attraction.

      Throw in factor that Foxit seems to require uninstalling / reinstalling more often...

      Comment


      • #4
        Yes, i am agree with you, reinstallation is not the solution but just a workaround, so i recommend you to do so if you are bored with this issue.And meanwhile, we will forward your comment to our QA and Dev team so they could have reference from customer and improve the program better and more stable.

        Comment


        • #5
          Thanks - you're correct - reinstalling may be the best short term fix. Honestly, avg users won't put up w/ this. If it was "common" to have to reinstall software, repeatedly, it'd be different.

          For many that don't have "screwed up machines / OSes," for mature, stable software, it's quite rare to repeatedly reinstall. Most apps just DON'T get screwed up - for me & most people I know. Of course, "try uninstall / reinstall" is common advice on any forum when users have probs. But I see that advice more on this forum than most, & personally gotten it from Foxit support, more times than ANY "professional" software I've ever used. That's a fact. Doesn't speak well of the development team. I'm not a coder, but something's wrong, somewhere.

          Under far less stable OSes, I've had entire suites like Office 2000 installed for yrs & never reinstalled / messed up once. To an extent, I think Foxit is shooting themselves in the foot. And I'm one that LIKES it. Millions of "avg", non tech users' apps reviews show - if it screws up once & there's an alternative, they drop an app like a hot potato.

          Comment


          • #6
            Uninstall or remove foxit cloudreading plugin, this problem seems fixed.

            Comment

            Working...
            X