Hi.
I've noticed that whenever firefox crashes - crash dumps get saved to the '%AppData%\Roaming\Mozilla\Firefox\Crash Reports' folder.
I think it's incorrect, because I'm a user of a portable browser and I expect to have all the browser related data in it's portable folder.
I've used Process Explorer and found out that process 'firefox.exe' has an environment called MOZ_CRASHREPORTER_DATA_DIRECTORY and it points to the '%AppData%\Roaming\Mozilla\Firefox\Crash Reports' folder.
Could you please make firefoxporable.exe handle that environment and make it point to '%firefox_portable%/Crash Reports' folder, please?
UPDATE: It also appears not to submit the data.
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
Follow us on Twitter
Could you please add a Bug with brackets around it at the beginning of your post title so it comes up in our bug tracker and gets more publicity?
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Done
This has been added in Firefox Portable 18.0. The crash directory is set to your Data\profile\CrashReports directory. That way it will work with custom profile locations and 2nd profile setups.
Sometimes, the impossible can become possible, if you're awesome!
I've updated my FirefoxPortable and I re-used Process Explorer to get the environments of firefox.exe again, and it reports that the path for MOZ_CRASHREPORTER_DATA_DIRECTORY is still the same.
I haven't yet crashed a Firefox (I don't know how to do that), but that's definitely not a good sign, so I can't yet confirm this bug is fixed.
I've used crashme to crash my instance and crashreport appeared in %appdata%, not profile folder,
so I change the bug status from [Fixed] back to [Bug].
p.s.: I've even tried to crash with AllowMultipleInstances=false because I've noticed that in that case FirefoxPortable.exe has a correct path for %MOZ_CRASHREPORTER_DATA_DIRECTORY% environment, but it still puts crash reports into %appdata% folder, instead of putting it into profile folder.
As always, AllowMultipleInstances is unsupported for functionality left behind. Firefox itself will not support or use the environment variable in that mode. Firefox Portable will always leave things behind in that mode. It's only for developers to use on their own machines.
If Firefox still stores it in APPDATA with the environment variable set, then it obviously doesn't use it. Where did you see it documented?
Sometimes, the impossible can become possible, if you're awesome!
Sorry, I think either you misread what I wrote, or I misunderstand you.
I tried 2 times: 1st time ini file was the following:
[FirefoxPortable]LocalHomepage=homepage.html
the 2nd time it was the following:
[FirefoxPortable]LocalHomepage=homepage.html
AllowMultipleInstances=false
And I didn't say a single word that I saw something documented somewhere. I don't understand your question.
The issue is still there for me, although I've downloaded a fresh version of firefoxPortable from this site (and I imported my profile and 'firefox' sub-folder into 'App' folder).
Where did you see MOZ_CRASHREPORTER_DATA_DIRECTORY documented? I don't think Firefox is using it properly if we have it set and it still stores it somewhere else.
Sometimes, the impossible can become possible, if you're awesome!
I didn't find any documentation about that, the only issue which is most relevant to the described problem is this one.
How do you think, is it worth filing a new bug to bugzilla.mozilla.org about this issue?
And yes, I've noticed that firefoxportable.exe now has an environment MOZ_CRASHREPORTER_DATA_DIRECTORY which points to the correct folder, and that firefox.exe doesn't inherit that value for that environment.
The question is: who's blame is this?
https://bugzilla.mozilla.org/show_bug.cgi?id=842209
John, is there a chance that you'd provide a patch for firefox to fix this issue?
Considering how insanely buggy crash reporting is, I think I will forcibly disable crash reporting in all future portable releases.
Sometimes, the impossible can become possible, if you're awesome!
The crash reporter is now disabled by default in Firefox Portable 20.0 and up. Upgrades are automatically set to disabled regardless of previous settings. You can enable it if you want, but it is not portable. A note to this effect is on the Firefox Portable homepage. This bug has been closed.
Sometimes, the impossible can become possible, if you're awesome!
Uhm, newer versions of Portable Firefox actually again invoking Crash Reporter.
Could comment this?
I installed Firefox Portable 28.0, opened up Options - Advanced - Data Choices. Enable Crash Reporter is unchecked. Is that not what you are seeing?
Sometimes, the impossible can become possible, if you're awesome!
Yes. And yet it still gets opened if a crash occurs.
Are you sure you don't mean the 'Firefox crashed' UI that happens on next start? Also, how are you crashing it?
If it's unchecked but still bringing up the crash reporter, then that's a Firefox bug, not a Firefox Portable bug, and not something we can do anything about on our end.
Sometimes, the impossible can become possible, if you're awesome!
No, I mean Mozilla Crash Reporter. I crash it as I already described above in this thread: I'm using crashme add-on.
I ran CrashMe on my local copy of Firefox with the crash reporter disabled and it still came up. So, either CrashMe is creating a non-standard crash (likely as it's not an approved extension and hasn't been worked on in 4 years). Or, Firefox has a bug with the crash reporter always being enabled. Not much we can do about either situation. I added a note to the Firefox page. The bottom line is that you can't restart Firefox from the crash reporter. It's not portable.
Sometimes, the impossible can become possible, if you're awesome!