I've been using current versions of Foxit in Windows 10 without incident since last fall, but this week after upgrading to v7.2, I noticed a rather severe problem that appeared after Foxit had been running for about 21 hours: Task Manager showed that Foxit's process was using an extremely high number of handles.
I noticed this because on a 16GB system, Windows came up with a "low memory" warning, something that I've never seen before. And sure enough, it showed that I was using about 15GB out of 16GB. Foxit's process wasn't using a high amount of memory, just handles, but a high number of handles is known for causing "low memory" problems. Upon closing Foxit, I suddenly gained back about 10GB. The system was back to its normal 4GB or 5GB overall usage.
I'll revert back to the previous Foxit version for now. Note that this was with the RTM release of Windows 10, something that I've been running for almost two weeks now. The previous version of Foxit had no problem with it. I bet this is a problem in Win 8.1 too, but I don't know.
I noticed this because on a 16GB system, Windows came up with a "low memory" warning, something that I've never seen before. And sure enough, it showed that I was using about 15GB out of 16GB. Foxit's process wasn't using a high amount of memory, just handles, but a high number of handles is known for causing "low memory" problems. Upon closing Foxit, I suddenly gained back about 10GB. The system was back to its normal 4GB or 5GB overall usage.
I'll revert back to the previous Foxit version for now. Note that this was with the RTM release of Windows 10, something that I've been running for almost two weeks now. The previous version of Foxit had no problem with it. I bet this is a problem in Win 8.1 too, but I don't know.
Comment