Threaded Mode | Linear Mode

Mele20 · Nov. 21, 2008, 07:08 AM

(Nov. 20, 2008 03:12 PM)lnminente Wrote: hehehe you are amazing PR!!! If i give you the imei of my mobile, what could you know about me? nothing more, only the government could across my network provider... Anyway i respect your thoughts (in old times i thinked like you), and are needed people like you, viva the nonconformists!!

Using file monitor from sysinternals, i see this file is created under the folder crash reports, so disable crash reporting. I fully understand the want to know from who comes the bug to later solve it.

Quote:Mozilla Crash Reporter is enabled by default and there is no user interface to disable it. Advanced users who prefer the standard application error notifications (e.g., the Windows error dialog "<application> has encountered a problem and needs to close" and Event Viewer record) can disable the Mozilla Crash Reporter by setting the environment variable MOZ_CRASHREPORTER_DISABLE to 1.
http://kb.mozillazine.org/Breakpad

I never allowed the old crash reports. I don't see how to disable this new crash reporter. It sent one report SILENTLY. That really pisses me off. Even Microsoft doesn't force you to send the reports (I frequently send them to Microsoft but it should be my decision each time and Mozilla has no business forcing this on users). Where do you set the "environment variable MOZ_CRASHREPORTER_DISABLE to 1"?

Since I didn't know where to set that I tried to do the second thing which is to disable it in the Firefox application.ini" file. But when I opened that file in notepad, I saw nothing about that. I just saw some text for what is shown the user when there is a crash.

This is on Vista, and it may be different on XP. I'll start the virtual machine with XP and Fx 3 and see. I found it easily in the application.ini file on Fx3 on XP. I must have scrolled past it on Vista. I opened it in notepad and that created a gigantic horizontal scrollbar so I probably scrolled by too fast to see it in Vista. I got disabled on both virtual machines that run Fx3. Smile!

Fx 1.5 (on my host XP machine) is using an ancient profile and crashing a lot now (I'm sure it's that profile causing the crashing as I have never before used a profile for half as long as this one before I had to create a new one) but I am so glad that on my host machine that I have never upgraded beyond 1.5. That was the last version of Fx where the developers still cared at all about the privacy of their users.