Help Us Fix Crashes!
We still get crash reports from a small portion of users. These are issues we aren’t able to reproduce here so we need your help to hunt down the buggers causing the crashes so we can squash them!
- Does Digsby crash for you at least once a week?
- Do you have Visual Studio installed?
If the answer to both questions is a yes, then you can help!
We created a debug version of Digsby that does a lot more diagnostic stuff under the hood. If you can get it to crash, the diagnostic log it generates will be extremely helpful in figuring out the cause. If you would like to help, here are the instructions:
- IMPORTANT: If you don’t have Visual Studio, the debug build won’t run.
- Download this file and put it in the Digsby folder. If you already have a “tag.yaml” file, edit it to change the tag from “alpha” to “debug”
- Restart Digsby so it can auto-update.
- Log in and click Help > About to make sure you now have build r24922 r24945 r24959 r24978.
- Next time Digsby crashes, if you get a dialog asking you to submit a crash report, submit one.
- Instead of telling Windows to close the program, choose to debug it in Visual Studio (prior experience would help)
- In the menu choose Debug > Save Dump As… and make a minidump of the current state of Digsby
- Email that minidump to bugs@digsby.com
Thanks for your help!
Update 1 (11/5/2009 5:45pm EST): We pushed out a patch fixing a crash related to viewing chat history in the log viewer. New release number is r24945.
Update 2 (11/6/2009 6:45pm EST): Another day, another crash fixed. New release number is 24959.
Update 3 (11/10/2009 5:10pm EST): Keep those reports coming and we will be crash-free in no time! New release with one more crash fix is 24978.








