Build 71 – Private Alpha Release
After a summer of non-stop feature releases, we are taking a little time to clean up the bugs, enhance performance, and tweak the usability of new features. Thanks for all the great feedback you are providing!
We just pushed an update to alpha testers (Build 71, r24743) which introduces lots of fixes and interface tweaks. As always, you can read the entire list of enhancements on our Change Log. Notable changes include:
- Fixed several of the most commonly reported crashes
- Fixed several significant memory leaks introduced in the last release
- Added diagnostic info to hunt down remaining crashes – please submit diagnostic logs if Digsby crashes
If you experience any issues please use “Help > Send Bug Report” in the main menu to submit a diagnostic log or email us at bugs@digsby.com.
If you would like to become an alpha tester and get new releases before everyone else, download this file and place it in the main program folder. Keep in mind that as an alpha tester you may get a release with a few bugs every now and then. We are looking for people who are proactive in reporting these issues so we can fix them before builds go out to all users.









Robert Said,
October 21, 2009 @ 1:39 pm
Nice work, I was starting to wonder when a new alpha would be released, it had been so long. Good to see you’re still busy bees, keep it up!
Flame Said,
October 21, 2009 @ 1:44 pm
Thanks for the windows 7 fixes. that no im windows showing up for the first hour really confused me. then it just went away
Lucas Said,
October 21, 2009 @ 1:58 pm
Oh, so it was Digsby that kept slowing my computer down with memory leaks? I was sure it was Firefox. Well, I hope the update solves that problem
Brandon Said,
October 21, 2009 @ 2:19 pm
Lucas probably still firefox, check out task manager from time to time.
Anon Said,
October 21, 2009 @ 5:26 pm
Does this alpha fix the pre-updater.exe crashing due to threatfire?
sean n Said,
October 21, 2009 @ 6:34 pm
Anyone else having the Digsby PreUpdater.exe crash when trying to update? bug report submitted
Kev Said,
October 21, 2009 @ 6:59 pm
So, after all the time, do you guys have a timetable for the Linux release? The only two choices for Linux seem to be Pidgin and Empathy – both IMHO suck. Digsby would clean up the Linux world me thinks.
You guys have been talking about the Linux release for awhile. You’ve cleaned up and fine-tuned the Windows release – time for Linux now?
sean n Said,
October 21, 2009 @ 9:50 pm
thanks steve for the quick reply turns out it was threatfire.
Carbonize Said,
October 22, 2009 @ 3:10 am
As of 3.5 Firefox’s memory usage is pretty good. Digsby’s memory usage is a bit ridiculous if you enable the social netowrking side of it but usually levels off around the 40Meg mark for me.
Digsby Said,
October 22, 2009 @ 8:14 am
@Anon + Sean: Threatfire has been notified of the issue here: http://digs.by/bbo If you are having this crash please report the issue to them.
Mike Said,
October 25, 2009 @ 6:53 pm
“A summer of non-stop feature releases”??????????????????
am i missing something?
Nicholas Chan Said,
October 27, 2009 @ 1:16 pm
Carbonize, lucky you. Digsby typically takes up 250Meg RAM on a normal day for me.
Gary Davison Said,
November 8, 2009 @ 1:07 pm
digsby is crashing with an error involving pre updater.exe for me too! ’shame as it was a nice program,’have to look elsewhere now..