New: Capture2Text (Sep 26, 2023), Platform 26.2.2.1 (Oct 03, 2023)
450+ real apps (49GB), 1.1 billion downloads, Please donate.
Jack Haller, Advisor and Father of Our Founder, Has Passed Away
When PngOptimizer Portable is launched it runs PngOptimizer64.
The problem is that there is a bug in PngOptimizer64 that causes it to crash on some 64 systems.
Becuse as far as I can tell PngOptimizer (32) run fine regardless of whether the system is 32/64.
I suggest that PngOptimizer Portable become a 32bit only program.
What's your source on this? I can't reproduce it on any OS and I've tried it on the 64-bit versions of Windows XP Vista through Windows 8.1. I'm running it on Windows 7 x64 right now.
The main program (64bit) will not run on ANY 64 bit windows system that I have access to , Win 7 and Win 8 both 64 bit.
If not a bug then what could cause the 64 bit version to crash when options are selected.
But the 32 bit version of the same program works fine.
And this is the only 64 bit program that does this to my knowledge.
I haven't gotten it to crash on any OS I've tried it on previously. Though, I did fire it up on Windows XP and it claimed not to be a valid EXE (could be the same bug as in 2.4 which was fixed in 2.4.1 32-bit only). So it would appear not to work on Windows XP which isn't that big a deal and can be worked around. I haven't gotten it to crash in Vista/7/8, though (options pull up fine, file compresses as expected, etc).
I haven't seen any reports elsewhere in a quick search for PngOptimizer crashes. So, it doesn't sound like an overall problem with the app affecting most users. More likely something specific in your setups that's triggering a less-obvious bug in the base app.
So, is there an antivirus/antimalware/firewall in common between them or some other configuration or app running in common with these machines? Have you contacted the publisher previously? What's the full path to where you've tried to run it from? This issue on your systems persists in the 2.4 release I posted today?
The latest realese (2.4.2) fixes the problem for me.
On the PngOptimizer Home page it says that the problem was due to
a change in the way Windows 8 (64) handles memory vs. Windows 7 (64).
And at the moment he doesn't have a Windows 8 (64) system , so the problem with Windows 8 (64) went unnoticed.
Until some kind person reported the problem and offered to test the fix.
I was wondering if it was related when I posted the update. Glad to hear it's working for you now.
Visit the Community page
Join our forums
Follow us on BlueSky