If i use Foxit Reader portable to open pdf document after closing the document foxitreader.exe and foxitreaderportable.exe do not exit. They are still in the task manager and consuming RAM. Is that a bug?
I am using Windows XP.
New: DesktopSnowOK (Jan 6, 2025), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Unless the main foxitreader.exe process closes, FoxitReaderPortable.exe can't close. It could be a bug in the base app, but I have not seen it myself.
Sometimes, the impossible can become possible, if you're awesome!
I guess i have to think about some autohotkey script that should close foxitreader.exe when i close a opened pdf document.
It works fine here when I open PDFs though it is slower to close than Sumatra PDF and other readers. Are you opening some specific document that may take longer? Is the CPU active?
Sometimes, the impossible can become possible, if you're awesome!
The documents i am opening are just pdf documents. The CPU is not active but both .exe files are consuming RAM.
May be this is happening only on Windows XP.
I just tried it on my Lenovo netbook running Win7 32 bit. No issues here. I'll try at work tonight where I have access to both Win XP & Win 8 64 bit.
**Update**
I just tried it on both systems with no issues. Could it be your pdf file? Did you try a different pdf file? That's the only thing I can think of, off the top of my head...
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
Peter8087 wrote:
(emphasis added)
Should your post be taken literally, then the answer is simple, it's not a bug, since Foxit Reader does not quit when all documents are closed, the way like, for example, modern web browsers do with closing the last tab.