If y'all's agreement with Mozilla allows it, anyway.
Portable Firefox just crashed on me, and when I tried to submit the crash report, it just said "There was an error submitting your crash report." Funny thing is, I'm pretty sure that it always does that. Firefox has crashed on me three, MAYBE four times since I've used it (to where the crash reporter comes up) and I don't remember it ever successfully submitting its crash report.
So if the feature's DOA, we can probably cut it to save space...? Or, is there some reason it's there? Because it certainly doesn't do what it claims, which tells me it either does something else, or is simply useless.
That would be an unauthorized modification of the Mozilla FF package. Any changes we have made in our distribution of FF have been specifically authorized. Mozilla wants our version of FF to be as close as possible to the standard distribution.
In addition, I do not think it would save that much space, but John can correct me if I'm wrong about that as I am not sure.
Tim
Things have got to get better, they can't get worse, or can they?
Right, didn't think about that. I suppose disabling the worthless feature would also be an unauthorized modification, too.
Crash Reporter behaves exactly the same for me too...
crash reporter takes up less than 200k. If you want to save space, you can disable the suspected attack/forgery options in security. That can get pretty massive.
I think it's because of a busy server.
It's works for me sometimes and then other times it doesn't.
But how much crashes does firefox have a minute in whole world??
I guess what you're saying is that Firefox doesn't crash very often, right?
While this is true, this is part of the problem. I see that crash reporter once a year at the most, maybe twice. And it "gets" me every time. I think, "oh, I can help Mozilla" and I type a sentence or two... and then it slaps me back down with that "could not send error report". It's such a let down. It's like "Oh, Mozilla really cares" and then "Oh wait, no they don't." Maybe that's a little harsh, but you'd think they'd fix it at some point. It's like they set it up and set the destination email address wrong, and now the guy who checks it thinks he's like the Maytag man or something.
I simly don't understand how after such number or versions the same error is displayed 80% of the time.