Anyone seeing very high cpu usage with RC1a?

[danward79]

Hi,

Had an urgent call out to day, from my study to attend a broken down HTPC in the lounge. :D

Found that the reason she was complaining that NR was not working was due to G4 RC1a having a very high cpu usage about 60% +

I was unable due to service time constraints, to further diagnose the problem. However, I have to say I am seeing this on my server too.

So I was just wondering if anyone else has done the "leg work"?

This morning on my server, I noticed a few dui error's in the log.

In the mean time on the HTPC, I have had to back track to B16

[Ron]

Sending you a pm.

[danward79]

Thanks Ron, got it.

Will let you know if I see it again.

[danward79]

Just installed RC2 this afternoon, and so far so good...

[mmoore99]

I, too, am seeing very high CPU utilization on both RC1 and RC2 (90% - 100%). This problem seems to be isolated to one specific computer. I installed on another computer and there is no excessive level of CPU utilization on that machine. This is occuring with just the basic install of Girder. There has been nothing added other than what the installation program puts there.

[Ron]

What CPU is that? Does the 100% persist (more then a minute) or is it shortlived?

[mmoore99]

What CPU is that? Does the 100% persist (more then a minute) or is it shortlived?It is a P4 1.8ghz. Yes, the high utilization lasts for as long as Girder is active.

[Ron]

Can you do me a favor? Close Girder and remove all plugins from the plugin directory.

Then test if the 100% CPU is gone. If yes then Close Girder add 1 plugin back start Girder. If 100 is not back add another until you find the culprit.

If the 100% CPU usage stays even without plugins then let me know.

[mmoore99]

Problem resolved. Following your suggestion, I isolated the high cpu usage to the audiomixer plugin. I then realized that the fact that I was using a remote connection to access the computer running Girder might be causing a problem. Upon checking I found that the remote control program was changing the sound driver which was causing a problem for the Girder plugin. When I removed the remote access from the equation everything works normally.

Thanks for your help.

[Promixis]

interesting... what remote access program where you using?

[mmoore99]

interesting... what remote access program where you using?I was using the "Remote Desktop Connection" program that is included in Windows XP.

[Mastiff]

Dangerous and cumbersome stuff. I have it turned off on all my computers and use Remote Administrator instead.

[Promixis]

interesting... what remote access program where you using?I was using the "Remote Desktop Connection" program that is included in Windows XP.

I use that all of the time and have not seen that issue. Is it definitely reproducable?

[mmoore99]

interesting... what remote access program where you using?I was using the "Remote Desktop Connection" program that is included in Windows XP.

I use that all of the time and have not seen that issue. Is it definitely reproducable?Yes, it is definitiely reproduceable. I did some further investigation and determined that the problem only occurs when the "Remote Computer Sound" option is set to "Bring to this computer" in the Remote Desktop Connection properties dialog (see attached screenshot). Having this option set causes the Remote Desktop Connection to change the sound driver on the remote computer to "Microsoft RDP Audio Driver". This seems to cause a problem for Girder.

[Promixis]

ok, will give it a try.

[Rob H]

I can confirm that this is a problem with RC3 - not tried it with RC4 yet.

It also seems to have nasty consequences if the screen saver kicks in on the remote machine - Girder doesn't come back from that and has to be killed.