Greetings!
It's not a big deal, but looks like my Firefox Portable 2.0.0.12 leaves folder in %HomeDrive%%HomePath%\Application Data\Mozilla\Extensions\{ec8030f7-c20a-464f-9b0e-13a3a9e97384}
As I understand this ID means "Theme" (at least I found it in every theme)
Also with Flash Player 9.0.115 it leaves file with some related stuff in similar place somewhere in .\Application Data\Mozilla\ but this file disappears sometimes, so I'm not able to tell right now what was there...
Similarly I found .\Application Data\Mozilla\Firefox\Crash reports\ with two files:
InstallTime2008030714
UserID
Edit:
I usually use UPX with "--ultra-brute --all-methods --compress-icons=0" on every ".exe" and ".dll" in "App" folder (to reduce FF size by approx 5Mb) so just in case I installed FFP anew (didn't compress it) and it still creates .\Application Data\Mozilla\Firefox\
Cheers!
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
%APPDATA%\Mozilla\Firefox is always created on launch. It's deleted on exit unless you have a local FF installed or you launch it with the AllowMultipleInstances on, in which case it will not clean up after itself.
Firefox Portable is not supported if compressed or if any of the JARs are recompressed.
Sometimes, the impossible can become possible, if you're awesome!
Sorry, didn't know. But still should it leave certain files behind?
Somehow I doubt it's because of compression...
But it doesn't matter...
Edit:
Yes, I use FFP with:
AllowMultipleInstances=true
So it should leave all data behind then?
Sorry, I must've overlooked this...
Reread what I just wrote above. It does create certain directories. But it deletes them on exit.
Certain betas of Firefox 3 Beta can cause the Crash Reports and Extensions directories to appear, but the current Beta 4 fixes that.
And yeah, AllowMultipleInstances prevents the cleanup routines from being able to work. The launcher wouldn't be able to tell whether it was its own firefox.exe or another still running. It's only made to be used on your own PC where you already have Firefox installed.
Sometimes, the impossible can become possible, if you're awesome!
Thank you and excuse me again...
I must've forgotten some things about FirefoxPortable.ini
It was long ago after all...
Cheers!
Wait, so there's no way to prod Windows into telling you the full path to a running process's executable, only the filename? Or am I misunderstanding?
It's not that really. It's the fact that another Firefox process is using those same things that the launcher would want to clean up. APPDATA\Mozilla\Firefox\pluginreg.dat, etc...
Sometimes, the impossible can become possible, if you're awesome!