I have heard of it happening, but I haven't been able to reproduce it, it's never happened for me. I think it may have something to do with the way I'm doing the network access right now, which is changed in svn… we'll see if it goes away.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It looks like there's a case where it can get stuck after network failure. That would make sense if suspend kicks it off. I'll do some testing and see if I can't resolve it in the upcoming release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm seeing high cpu usage when googsystray is start before internet connection is established. Even after internet is connected, googsystray is still using almost 100% cpu cycle and it doesn't work. If I restart googsystray, it works again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sometimes (I don't see a pattern yet) googsystray will start using a lot of CPU power for no apparent reason. Is this a known bug?
I have heard of it happening, but I haven't been able to reproduce it, it's never happened for me. I think it may have something to do with the way I'm doing the network access right now, which is changed in svn… we'll see if it goes away.
It seems to happen only when I resume from suspend.
Are you using the Wave support?
Yes: gmail, gcal, and wave.
It looks like there's a case where it can get stuck after network failure. That would make sense if suspend kicks it off. I'll do some testing and see if I can't resolve it in the upcoming release.
I'm seeing high cpu usage when googsystray is start before internet connection is established. Even after internet is connected, googsystray is still using almost 100% cpu cycle and it doesn't work. If I restart googsystray, it works again.
Can anyone note whether or not this is fixed in the 1.1.x series?
It appears to be fixed now. Thanks!
It doesn't do it any more….I guess it's fixed. Thanks.