// you’re reading...

How in the Tech

Why Firefox Caught Fire


Similar to Microsoft’s random program has encountered a problem and needs to close crash dialog, the fine folks at Mozilla have the same idea included within the Firefox browser. These crash reports are vital to the developers who are tasked to fix the bug you just experienced. While the reports rarely make sense to us users who take the time to glance over them before sending them along the way, they are helpful to the select few.

If you are like me, you are probably not even aware that these reports are happening in the background. At one point or another, you agreed to send the information along - and it wasn’t in a sneaky EULA license you blindly clicked through. Instead, at the time of that first browser crash a dialog pops up that solicits your permission to send the debug report back to Mozilla.

But did you know it’s possible to see all the crash reports in mass, after the fact?

In your Firefox address bar type about:crashes and hit enter.

Now click on any crash report to get it’s details. Helpful? Maybe to some of us.

If you want to be notified the next time I write something please subscribe to my RSS feed. Thanks for reading!

Related Posts

Discussion

No comments for “Why Firefox Caught Fire”

Post a comment