Firefox Portable 13.0.1, Thunderbird Portable 13.0.1 and SeaMonkey Portable 2.10.1 leave behind an empty folder within $LOCALAPPDATA of Mozilla\Firefox, Thunderbird and Mozilla\SeaMonkey respectively. This is a result of a newer version of the underlying engine so the Firefox and Thunderbird 10 ESR releases are unaffected.
The issue has already been fixed in Firefox Portable 14.0 Beta 10 and Thunderbird Portable 14.0 Beta 4 and will be fixed in the next release of Firefox and Thunderbird Portable. As a workaround, you can use the launchers from the current beta releases of FFP and TBP with the stable releases to fix the issue now.
This bug will remain open until the next releases in about 6 days.
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
This is now fixed in Firefox Portable 14.0.1 and Thunderbird Portable 14.0. I'm going to leave this bug open until SeaMonkey 2.11 drops later today.
Sometimes, the impossible can become possible, if you're awesome!
Also TBP 14.0 and FFP 14.0.1 leaves behind in %LOCALAPPDATA% the empty folder Mozilla\Firefox as well as Thunderbird.
The Mozilla\Firefox and Thunderbird folders are both cleaned up as expected on my work computer (WinXP SP3).
Do those folders exist before you run the apps?
I have removed the both folder Mozilla\Firefox and Thunderbird, which are contained in %LOCALAPPDATA%. Afterwards I run FFP 14.0.1 and TBP 14.0 and both folders will created again. I also use WinXP SP3.
Did you close Firefox Portable before checking?
Both work here as expected. As did the betas before them. Note of course that setting multiple instances voids this behavior.
Sometimes, the impossible can become possible, if you're awesome!
Excuse me, of course both apps work correctly as expected.
Does that mean you had multiple instances set?
Sometimes, the impossible can become possible, if you're awesome!
The reason for my fallacy was, that I have overlooked the fact, that the launcher removed the empty folder after closing the app.
I also detected in the folder layout, that there doesn't exist the typical folder "Launcher" and a file FirefoxPortable.ini. Therefore all settings are contained in the launcher, so that it's not necessary to include such a FirefoxPortable.ini file. Is this so far correct?
Once again I want remember at this point on my 2 other posts Creation of a Plugin Installer and Plugin for PhotoFiltre Portable 7.0. Why do I get no answer?
I can't say anything regarding your plugin dev posts, I have never made a plugin installer myself and wouldn't be much help, but I do know that Firefox uses a custom launcher instead of the regular PortableApps Launcher and therefore does not have a FirefoxPortable.ini file.
As this is now fixed in all Mozilla apps, the bug is closed.
Sometimes, the impossible can become possible, if you're awesome!