I run Firefox Portable off of my USB drive, which sometimes has a loose connection. So, occasionally when I'm browsing, Firefox will just crash. I'll check the drive, find that it's not connected, reconnect it, and continue browsing--but it is still a problem.
I am wondering if there is a way to change this in about:config so that instead of crashing, Firefox can let me know that it can't access its files, then I can reconnect it. Or maybe this is an update that I can suggest?
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
It'll just crash. An upcoming platform release will kill it for your and let the launcher clean up. But there's no way to let Firefox run from it and not crash or close. A better option would be to copy it locally and use it and then copy it back. Or fix your flash drive.
Sometimes, the impossible can become possible, if you're awesome!
Hmm, the launcher cleaning up is a good idea, but will it work? The way Windows works, it doesn't read an entire executable into memory at once (otherwise 100+ MB NSIS installers would take forever to start up ;)): the code is loaded as needed and then cached. Which means the crash cleanup code might not exist in RAM until the first time it's called. This is fine in case of a "normal" crash (e.g. bug in Firefox, Flash, other misc. plugin), but if the disk that contains the code has been removed, how can it run then? The OS would crash the launcher in this case too, would it not?
Nope, it works. I've tested it on a couple PCs and OSes as well.
Sometimes, the impossible can become possible, if you're awesome!