Sometimes I forget that I already launched PA.c Platform and launch it again. Nothing happens and I see that it's already running. I then quit it and next time I try to launch it, nothing happens. I have to start Task Manager and kill all running PortableAppsPlatform.exe processes before it can start up again.
OS: Windows 7 32-bit.
This does not happen on my other PC with Windows XP.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Looks like Google Chrome is what causes this, again. Here are steps to reproduce:
1. Start Google Chrome
2. Launch PA.c Platform
3. Start some portable stuff from it, I started Opera Portable.
4. Launch PA.c Platform
5. Start Task Manager and find two PortableAppsPlatform.exe processes running
6. Close Google Chrome - additional PortableAppsPlatform.exe process dissapears.
Based on the OP's comment, I'd say this isn't a bug relating to the platform at all, and as such, should be closed. Thoughts?
No. It is a problem within PA executable. There was a similar problem with LibreOffice Portable Launcher, check this thread: https://portableapps.com/node/32165#comment-194531
As indicated in that thread, the problem is with Google Chrome, not with the PortableApps Platform.
That's the same problem as here.
True, but as previously indicated, a fix was a applied to both LibreOffice Portable and the PortableApps.com Platform to work around Google Chrome's unresponsive window. So, it should close regardlesss.
Sometimes, the impossible can become possible, if you're awesome!
But this bug came out way after you said it was fixed. Can you double check it's really fixed and the fix did not dissapear from build system? Or it was only fixed in recent PA platform update? I did not check it after I made this topic.
It was re-introduced. I have a patch built and will update to 11.0.1 shortly.
Sometimes, the impossible can become possible, if you're awesome!
No, the problem is caused by Google Chrome, but definetely not because a bug or something in Google Chrome. It must not respond to anything, that's why there are timeouts. Bug is in the PA code setting timeout to 0 causing infinite wait for windows that do not respond to a call. Obviously, it's kinda lame to blame Google Chrome for that.
This issue is fixed in the 11.0.1 release just posted. 11.0 users will get a 1MB fast-install patch rather than a full platform download.
Sometimes, the impossible can become possible, if you're awesome!
Thanks! You are awesome.
You're welcome. We aim to please. I didn't want a nasty bug like that sitting unpatched. And it's far faster for users to update now with incremental updates, so we don't need to feel as bad about pushing out a quick patch.
Sometimes, the impossible can become possible, if you're awesome!