guys i've got a p4 ... 1.5Gb ram ... do you think i can install

and run smooth...

I had this bug. Bravo to whoever figured this one out. I owe you a beer!

This just started happening to my today on Vista X64. On my system the mouse pointer thing was already UNCHECKED but I checked it and it stopped the high cpu usage.

Yup.. I got it too.. 8% CPU without pointer shadow, 0% with.. On Vista 32 bit SP1. But hey shadow/no shadow whatever keeps Digsby happy.. :)
Are you using WPF? That sure explains some of the sluggishness (is that a word?) that's been reported. MS probably will keep improving on that..

this happens to me daily. Any Progress on this?

this bug actually still exists in windows 32, it was happening to me a couple days ago

Wow, I didn't even know this was happening as I have been running F@H. Now I might even get better performance with F@H too. Wow. What a strange bug.

hmmm....i have a good bug for ya guys! I actually now have 2, and, yea lol. So, here's the story, and all of what i had to do (JOY for everyone! oO)

So, i logged off digsby, as i normally do to get the update (*note, i'm actually here more than i'd like to admit lol) - and, normally it installs proper. Oh, by God...and, today would just HAVE to be one of those days where nothing's going right on here lol. So, i downloaded the file off the forum, tried to install it that way - and nooooooo...what do we have here??!?!? won't install cause of .dll files, blah blah blah.

So, i restart...wait for it to start up, uninstall digsby - and, delete the folder from C drive :D - always a joy when ya have to go into the computer ya know (Steve, i'm NOT 'bitching'....cause, i do know how hard it is to get...technical oO lol) - and, c'mon, you're gonna take me out of the thrill of beta testing! NOPERS! :D

Run the install again from where i downloaded it too - and after installing it again - IT WORKS! So, i tried sending this in a bug report....and, the log wouldn't go through LMAO!!!!

So, after all that....this is what my conclusion is. My net's screwed up, and has been all day...and, i dunno if that's cause i was seeding my torrents - or, what, who the hell knows lol. So, i'll go take a look at that - and see if it's on my end or not (awww....i was gonna play pogo *cries inside* lol.

But, hey, if it's a bug - i finally found one!!! (Just, don't get my hopes up lmao)

Man I hope a new version with IRC comes out soon..I use Trillian Astra here and there but mostly 3. Digsby is just so much better but IRC is so necessary for me =P

I know this is unrelated, but is there a way to have disby be the one to respond to website clickable links to IM someone?

I don't know if this is a bug or not, but whenever my one friends (who uses trillian) signs on or off it doesn't give me a notification. To my knowledge he's the only one this happens too and he's the only one of my friends that uses trillian. Also all of my offline contacts say that their status is "unknown" which just started happening recently. Have any ideas what could be causing this?

Has anyone ever noticed that when IMing another Digsby user, sometimes they don't get the IMs that you send? Especially if it's a copy/pasted link, and it's a new conversation? It happens pretty regularly.

The pointer shadow being off seems to cause more then just cpu ussage by explorer.exe. As soon as I turned it on, it removed a sluggishness / lag issue that I have been experiencing with the newer testing builds of digsby.

Can you please just release the Mac version already, before it's too late!

I really love Digsby!

The only bug i got is when im trying to connect, it says "connection failed, try again in 4minutes" ._. (but it only happens sometimes!)

:O!

Ok, so ive had a couple issues this week with Digsby, im using WinXP SP3 32-bit and have noticed both minor and major memory usage spikes, but the most recent one was like 10min ago, Digsby had been running about 2 solid days so any updates were not recieved until i just quit and restarted it, but here's a picture of the 249MB memory spike i just hit, im hoping its an isolated incident or something, but figured i better report it.

http://img291.imageshack.us/my.php?image=digsby...

I use a PC at work and love Digsby.

I use a Mac at home and hate my options.

When can we expect the Mac build?

... and I have forgot, I use Digsby build 15142

I use Windows Vista 64bit SP1 (build 6001) with czech localisation and I have not experienced this bug..

Yes, affects me as well. Windows Vista SP1 32-Bit

Digsby eating 1.5 GB of RAM, just like James above... But I'm using XP. I have a screenshot saved off...

This CPU usage problem is not limited to just 64-bit Vista. I had the same problem with Vista SP1 (32-bit)

Using Mark Russinovich's "Process Monitor" shows that while Digsby is running, Explorer.exe is constantly opening Registry Keys related to my Nvidia display adapter.

Take a look: http://i111.photobucket.com/albums/n136/jonah19...

Yeah, I will say, for this being beta, this program runs way better than Pidgin and Trillian combined. The Facebook features are especially awesome. Running it on Windows Ultimate x64 and it seems to be running fine so far after having computer on for couple of days.

I just tried Trillian Astra, and I have to say, even though it looked cool at first, it was nowhere NEAR as good as Digsby is.

Its functions were not nearly as customizable, it was bloated, it didn't have Facebook chat or gmail/gchat, and the only good thing about it was the looks. And looks are deceiving.

Go Digsby! :D

So...
Whats next for Digsby?

yeah have the same problem

BUT I HAVE WINDOWS VISTA ULTIMATE X86 WITH SP1!!!

my cpu usage was on 30% !!!!
digsby was lagging extremely

do you already know, what causes this bug? devs?

@ leebe

ooooooooo thank you very much =) all fixed and back to normal. excellent

Oh my god, this was my problem!! I was at the point I was going to stop using Digsby completely because not only does this bug sap 8% of the CPU through the explorer process, but Digsby itself was EXTREMELY laggy to use and completely unbearable.

Imagine a single-core computer with a process sapping 99% of the CPU, then while that is going on you are trying to use Digsby. Clicking, moving the window, even typing was laggy as heck. That is exactly what was going on with this mouse bug, which DID fix the problem.

You should note my install of Vista 64bit comes with the mouse shadow disabled by default. I am sure other Digsby users are having this very problem.

That is a very interesting bug find, haha. Where/how do you submit bug reports to Microsoft? I've heard horror stories about the process. :P

..back on the Linux topic, I'm afraid that the Linux build will be a no show project...or at best be slowly developed after the Windows build is stable and the Mac build has been stabilized.

If they are coming one by one then we could be waiting far too long on a Linux build.

what I think would be neat, is to have a digsby widget for Vista. I isntalled Vista the other day, and although I'm not a big fan of it, the widget system is kinda neat... a mac widget would be neat too.

The weirdest bug I've seen was with Trillian.
Whenever I would start up Trillian, before switching to digsby of course, it would crash the taskbar over and over and over again, it an endless loop of crashes.

Of course, ya know curean studios (sp?) they didn't even want to address the problem, because it was just so "off the wall". After version after version with this same problem, someone on their forums FINALLY stepped up and told us what the bug was caused from. It was some sort of conflict between Trillian and Panda Antivirus+Firewall 2007. I don't know if Panda 2008 has the same conflict with Trillian or not, but that whole Fiasco was the whole reason I ditched Trillian, and have NEVER looked back since. They were downright RUDE to me when I reported this problem. They kept telling me it was MY fault somehow, and I knew I wasn't the only one having this problem, that reinstalling my OS wasn't the fix to the problem, and then when someone else reported the same problem, and a solution, in the forums, did they appologize to me for being so rude!? heck no! they were even more rude yet. From what Panda told me, it was a Trillian problem, but CS didn't want to address the issue so Panda had to develop a workaround, thats what was really sad to me.

but yeah it was the strangest bug I've ever seen. The Windows 95/98/Me/XP/Vista taskbar just kept crashing and crashing and crashing over and over and over as soon as I would start up trillian, and would not quit the cycle of crashes until you exited trillian, which you couldn't do if it was minimized. I would have to restart my computer to get it to stop, wasn't til I discovered exiting trillian got it to stop when trillian wasn't minimized and could get to the exit menu to discover it was only happening while trillian was running. hehe

As you can imagine, it was probably just a memory leak in their code or something that would crash the taskbar, its the fact that they wouldn't address the issue that got me, that someone outside of the company had to discover what was causing it. heh.

This one's pretty crazy, just happened to me now. This is with the latest stable build. I noticed it was running slow, but have NO idea what caused this!

http://www.thalagyrt.com/files/digsbyram.png

~1.05 GB of RAM usage!

so when is this going to be fixed? its quite a shame that performance users on windows x64 are hit the worst by this.

@serah

This happened to me when i first installed the beta. It was caused because i had a custom message skin remembered by my digsby account but when u install the beta u lose all of your stored themes. So basically its trying to use a skin that no longer exists. Simply reapply a default message skin or re download and install your old one to get things working.

@Steve I hear ya! Don't release it before its ready..but......when you say "once the Windows build is stable" - does that mean never? ;-) Are any Windows builds "stable"?
In all seriousness, I've had no issues with any version of Digsby in regards to memory, CPU or disruptive interface issues. I run the beta at work and the non-beta at home. Both use about 10 MB ram when idle and both return unused RAM when returning to idle. [XP SP3, AMD Athlon X2, 4 GB RAM]

i tried the beta build. first thing i noticed was that when i was sending an IM, it would be sent, but i would see nothing in the box. i just get a white screen. i know the other person is getting the message because he responds which i can see as the little bubble on the bottom left corner but not on the actual IM box, which just stays white. So I uninstalled it and reinstalled the stable version but for some weird reason, I still get the same bug. help! i'm currently digsbyless... =(

Yeah by sheer luck I happened across this solution and thought no one would believe it it was so odd hence the video :)

@Kejlsn: Turning on cursor shadow alleviates the issue but obviously doesn't fix the bug. I think it is something Microsoft will fix but we added a ticket in our system to see if we can figure out how we are causing it to see if we can avoid it from our end.

Ok, soo...I was taking action in that forum thread too because I use Vista64 and had to deal with that bug too! But, now when I read this latest blog-post, I can't see if you fixed the problem, if you will fix it later, or if it's nothing you can do at the moment becasue the problem is in Windows and not in Digbsy?
My brain may be slow now, I'm confused :S

seems to be fixed with one of the stability updates which you can download only from microsoft site...
i always install those updates and don't have that bug :)
a list with all updates not included in windows-update is here: http://aaron-kelley.net/downloads/hotfix/

I just sent in an email, but I get a different default 'from id' when I double click on a contact than when I right click > chat.
The one i get when i double click is the one I don't want, and doesn't seem to remember when I change, close, reopen. The one when I right click > chat is the one I want & use.
I don't get it with all contacts, just one so far...
I've noticed it in both b17003 & 17031, I believe.
I have deleted & re-added the contact.
How's that for weird ;-)

So is this an issue with Digsby, or with Vista x64? Someone should send this video to the people at Microsoft so they can push a fix for it!

@Gabor: That should not be happening at all. Emailing you for more info to see if we can figure out the cause.

I don't know if it's a bug, but whenever I try to open a window in Digsby or scroll in one, my CPU usage climbs up to 50-60%... And that's with that latest test-build (r17003), that should've improved rendering/drawing of windows.

Can't really post a video, but Digsby feels sluggish as hell on this computer (P4 3Ghz, 3Gb ram, WinXP Pro SP3), sometimes I have to wait 6-10sec before I can even start scrolling, while at home (Intel E8400, 4Gb ram, Vista64) it runs smoothly. But that's probably because I got a whole lot more powerful hardware in that one.

@Nisah: Once the Windows build is stable we will release. We don't want to spread ourselves thin.

That is truly a most Epic bug, bravo for discovering it! :)

Which makes me wonder....
When are you going to be finished with the Linux version of Digsby?

I got to write the bug report/ticket for this. The title: "Disabling cursor shadows in Vista64 causes digsby to make explorer.exe use CPU". It's a nightmare of a run-on sentence of a title! =O