BugSplat is a crash reporting tool used by developers to find when their software crashes while in use. Today BugSplat helps companies find and fix bugs in their software for 250+ million installed applications around the world.
You’re likely reading this because something popped up on your computer saying it’s from BugSplat. That pop-up probably looks like the image below.
That popup is called the BugSplat Crash Dialogue and it is only seen when a software application or game that uses BugSplat crashes while in use.
It is only viewable at that time because BugSplat is a program called a crash reporter and it's job is to report when crashes happen.
As a crash reporter, BugSplat helps software companies understand how their application performs for their users by reporting on instances of crashes.
Software companies that use BugSplat are hoping that knowledge of software crashes will help them improve their applications.
Today, BugSplat is used by many companies large and small to fix bugs in all kinds of software and video games. You can learn more about how BugSplat specifically helps companies fix bugs on our Features page.
You will only get a "BugSplat" (i.e. see the BugSplat Crash Dialogue) when a software application you are currently using crashes. A crash is something that occurs when a softtware application runs into an issue or defect that causes it to break.
Once a crash occurs, a BugSplat crash dialogue appears to ask for feedback from you about what caused the crash.
Including details about what immediately happened before the application crashes is a powerful way for developers to fix the issue you just experienced. Feel free to let the developers of your application know what happened.
BugSplat is very useful to software companies because it lets them know how stable their software is while in use. This helps them prioritize things to fix as well as saving time fixing things overall.
To show you precisely why BugSplat is useful, we'll use a fictional software company named ACME Software as an example.
ACME Software is a company that is about to release a new version of its software to the thousands of users who use it every day.
In the past, ACME had heard complaints from their users that their software wasn't stable enough and crashed too frequently.
To improve this, ACME decided to use the BugSplat crash reporter to understand how often their software was crashing for its users.
Before releasing their new software to users, the developers at ACME added BugSplat to their application code. This allowed their software application to report back to them whenever it crashed.
After the ACME team finished this process, they did a little more testing, and then they shipped the new version of their software application to their users.
Once their users had the new version of the ACME software, they used it the same as they always had.
However, when some users started running into an issue that caused their application to quit unexpectedly, the ACME software program called the code included from BugSplat to capture the crash.
At this point, ACME users saw the BugSplat Crash Dialogue box and were asked to describe what caused the crash. The dialogue box also allowed for users to leave contact information for ACME to contact them about a fix.
Because ACME had BugSplat included with their software, they quickly learned about the problem in their code. ACME took data collected by BugSplat to find the cause quickly. They fixed it and shipped a new version to their users that didn't crash as often.
Because ACME is was now using BugSplat, they had a much better understanding of how stable their software was because they have an accurate crash count and data on what causes their worst crashes.
Here’s what we've been up to recently.
Join our other subscribers for product updates, crash reporting and development best practices, tips on running a startup, and deep dives into video game history.