Seems like it is profile-related thing, because it happens with my working profile and does not happen with the clean one.
How to fix this issue?
New: Run-Command (Dec 2, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads Nov/Dec!, Please donate today
If it works with one profile and not another, it's not the launcher having an issue. It's Firefox closing immediately due to a corrupt profile, at which point the launcher will then close. Try starting it in safe mode (by passing -safe-mode to the launcher itself on the command line or using the FirefoxPortable.ini and setting it in AdditionalParameters=).
Sometimes, the impossible can become possible, if you're awesome!
no, firefox.exe works fine. The browser is completely usable. But firefoxportable.exe doesn't live for more than 3-4 sec with that profile.
Do you have it set for multiple instances? If so, that's why.
Sometimes, the impossible can become possible, if you're awesome!
Thanks for the tip. That was the reason.
Is it correct behavior or is it a hack?
can't firefoxportable.exe handle multiple instances of Firefox properly? Why not?
The ability to run multiple instances is only partially supported. And it will result in some files being left behind on the local machine. Additionally, Firefox is unable to open files passed to it when set in this mode as the starting instance can't determine which running instance to pass the file to. Basically, the ability to run multiple instances in Firefox itself is really only intended for developers to test bits out. We make it available via the launcher for advanced users that need to run two different copies at once on their local machines or portably if they don't mind leaving minor bits behind.
Sometimes, the impossible can become possible, if you're awesome!
I find it interesting that it works differently for Thunderbird, which in so many respects is just like Firefox. The launcher never terminates till you exit Thunderbird.