sorted by: recent | see : popular

Content Tagged with crash + Development

With every release, we’re doing our best to make Songbird more stable. We know, however, from time to time users encounter unexpected hiccups. We genuinely want to address these issues! Here’s how you can help make Songbird better if you notice a problem.

We have put together the following suggested steps that you can consider performing in the event of a Songbird crash (and no, they don’t involve removing your seat cushion and holding it tightly to your chest):

• Tell us about it!  Please choose to report the crash through the Crash Reporter interface.  Your crash reports are completely anonymous and free of personal data (including browser history, library content, and application configurations).
• Drop us a line and include the Crash ID number!  The crash reports are anonymous, but you don’t have to be.  The more you can tell us about what you were doing at the time of the crash, the better.  There are a few ways to contact us:
  • http://bugzilla.songbirdnest.com — Log a bug about your crash
  • http://getsatisfaction.com/songbird — Post to the forum about your crash
  • support [a t] songbirdnest [d o t] com — Send us an email about your crash (we may choose to log a bug using this email, and we’ll keep you in the loop that way)

Once we hear from you and have some additional data to go on, one of our highly-skilled Bird Surgeons will begin looking for the source of the problem. Thanks for your help!