Re: Exodus 100% CPU on Windows XP

Paul Clegg <[email protected]> Fri, 13 May 2005 09:18:41 -0700
Newsgroups gmane.network.jabber.exodus.user
Message-ID <[email protected]>
Are you using the "Queue offline messages" feature? We've had luck avoiding 
this behavior by disabling offline queuing.

I've also observed similar behavior after a long idle time as Exodus 
dispatches all the notifications (sound, etc.) when you return to available 
status.

Perhaps some sort of maximum length should be placed on the 
notifications/messages stored when idle away?

-Paul

On 5/13/05, Brad Morgan <[email protected]> wrote:
> 
> >
> > If my workstation is idle for a long time (3+ hours) and if
> > someone sends me
> > a message during the time when I come back I see Exodus open task
> > in the XP
> > tray highlighted but clicking it will not open the chat window. In every
> > instance the task manager shows 100% CPU consumption by Exodus
> > and naturally
> > none of my other applications work until I END TASK Exodus.
> >
> 
> I'm having exactly the same problem. Is there a workaround? I this the
> proper place to report this? If not, where should it be reported?
> 
> Regards,
> 
> Brad Morgan
> IT Manager
> Horizon Interactive Inc.
> 
> _______________________________________________
> Exodus mailing list
> [email protected]
> http://mail.jabber.org/mailman/listinfo/exodus
>

_______________________________________________
Exodus mailing list
[email protected]
http://mail.jabber.org/mailman/listinfo/exodus