Testers Needed for New Release!

Did Digsby install Microsoft Visual C++ 2008? Cause if it did, it put alot of crap in my C:\.

I noticed that too. I hate it when apps drop junk in existing folders or in this case, c:\.

There is still a bug when Opera is set as default browser. The inbox will not open (for mail). I've sent a bug report.

Other than that the release seems faster and better this time. Good work!

Last edited by xbyte (2008-08-09 11:54:31)

with the new build all my IM windows have been resized, they're all way to small to chat normally, so i have to resize them manually as i open them, and since digsby doesn't retain the size of the windows you have to do this every time you open a chat window.

with the previous builds it also didn't remember window sizes, but the windows were coincidentally already the perfect size.

edit: seems i was wrong initially, digsby does remember the size now, however the default size is much too small.

i might be a little obsessive but i prefer all my im windows to be the same size, so a larger default size, like the size in the previous build would be preferred, at least by me, so i don't spend my days obsessively resizing every window so it's approximately the same size as all the others.

and yes i know i have a problem

Last edited by Brandito (2008-08-09 12:03:21)

just wanted to say, so far we're getting great feedback; here, but some great stuff in bug reports as well.

thanks guys!

mika wrote:

I noticed that too. I hate it when apps drop junk in existing folders or in this case, c:\.

I read on MSDN that Visual C++ 2008 Redis. SP1 will fix that funk droping problem.  Also, anyone know why Digsby causes my explorer.exe to use 7-9% cpu usage?? Will try a clean install to see if it happens again.

I did not have any problem installing or while using it till now, but my Comodo firewall and anti-virus heuristics detected it as a possible malware when i tried logging in. This was not the case with the previous digsby.exe executable. I have attached the snapshot of the comodo's message and mailed it to bugs@digsby.com. Please mail me or contact me for any further detail required.

Digsby did just crash without a reason or notice. (No crash assistant.)
I sent you a Bug/Crash report.

Last edited by philipp_grunwald (2008-08-09 18:45:16)

Digsby is still unusable for me.
Bug described here http://forum.digsby.com/viewtopic.php?id=1714 still exists

Anyone get a memory leak as bad as mine (Over 500MB of RAM)?
I submitted a bug report, but everytime I minimize digsby, it drops down to about 15-20MB, but climbs right back up after and hovers at around 500MB.



EDIT: Exiting and restarting digsby seemed to have stopped it, not sure what caused it though.

Last edited by bobbyd87 (2008-08-09 18:42:15)

amazing guys! i went from my typical 112MB to 20MB! one thing i've noticed is that digsby will use like 5 - 8MB then when you send or receive an IM it will spike to 20 - 30MB

wyldstallyns2589 wrote:

amazing guys! i went from my typical 112MB to 20MB! one thing i've noticed is that digsby will use like 5 - 8MB then when you send or receive an IM it will spike to 20 - 30MB

I noticed this same behavior when the buddy window is open and then I hover over a person's name.  RAM usage hops up to 20-30MB before it displays the popup buddy info window, and then it'll drop to 5-8MB when you leave the buddies name and the popup hides.

Just wanted to check something with you guys...

I can see my root directory (d drive where the install file is) have some files from "Microsoft Visual C++ 2008 Redistributable Package". I'm not sure if Digsby is the reason, but that's the case Digsby should use Windows own temp file locations. I don't like a mess of files there for no good reason.

Last edited by xbyte (2008-08-09 19:36:57)

bobbyd87 wrote:

Anyone get a memory leak as bad as mine (Over 500MB of RAM)?
I submitted a bug report, but everytime I minimize digsby, it drops down to about 15-20MB, but climbs right back up after and hovers at around 500MB.

http://img293.imageshack.us/img293/7448 … zs0.th.gif

EDIT: Exiting and restarting digsby seemed to have stopped it, not sure what caused it though.

Mine did that yesterday.  Has been running fine though since I did the restart.

Aithne wrote:

bobbyd87 wrote:

Anyone get a memory leak as bad as mine (Over 500MB of RAM)?
I submitted a bug report, but everytime I minimize digsby, it drops down to about 15-20MB, but climbs right back up after and hovers at around 500MB.

http://img293.imageshack.us/img293/7448 … zs0.th.gif

EDIT: Exiting and restarting digsby seemed to have stopped it, not sure what caused it though.

Mine did that yesterday.  Has been running fine though since I did the restart.

I took a quick look at your bug report, Aithne.  Looks like there were sockets (or at least a list of file descriptors) leaking, which eventually triggered a cpu/logging spin.

I've sent two bug reports now, and the problem seems pretty repeatable. Just browsing through the IM window skin list causes Digsby to crash. It's not a particular skin that does it, just going through 'too many' choices.

Good work on everything else though. I can hold conversations in MSN, Digsby doesn't leak, and my IMs and emails are all in one place.

Last edited by VioletArrows (2008-08-09 20:52:34)

chris wrote:

Aithne wrote:

bobbyd87 wrote:

Anyone get a memory leak as bad as mine (Over 500MB of RAM)?
I submitted a bug report, but everytime I minimize digsby, it drops down to about 15-20MB, but climbs right back up after and hovers at around 500MB.

http://img293.imageshack.us/img293/7448 … zs0.th.gif

EDIT: Exiting and restarting digsby seemed to have stopped it, not sure what caused it though.

Mine did that yesterday.  Has been running fine though since I did the restart.

I took a quick look at your bug report, Aithne.  Looks like there were sockets (or at least a list of file descriptors) leaking, which eventually triggered a cpu/logging spin.

Was that a one time deal or something I should be keeping a watch on?

Aithne wrote:

Was that a one time deal or something I should be keeping a watch on?

I'd go with the latter, as I'm not sure what caused it, though I didn't look that close.

chris wrote:

Aithne wrote:

Was that a one time deal or something I should be keeping a watch on?

I'd go with the latter, as I'm not sure what caused it, though I didn't look that close.

Alright then, I will keep a watch.

Guys, when i'm playing a song now....sometimes it changes, sometimes it doesn't (For my status) - i'll send a bug report But, now, why do i get a thing for a http://www.snipr.com/ link? i checked it out to see if got hacked or somethin, but, it's like a Snipper for URL's and stuff. So, i dunno. Kinda weird - it shows it in my status bar link - when i send the bug report - you'll get the screenshot...maybe ya can help me make sense of that stuff lol.