ASGS client causes 100% CPU load

Flower · Post by **Flower** » Sat Jul 15, 2006 9:13 am

Hi all! I just noticed that my ASGS Client causes a very high load to my CPU.

I am not completely sure wether this High Load impairs other processes and effect my ingame experience. Yet I would assume that it does not as I have switched ASGS to Idle priority and Alleg FPS did not change.
Still the thought that ASGS is keeping my CPU warm for me is not one of my favorite things.

I took a screenshot as a picture commonly explains more than words:

As well did I find this thread that seems to be connected to the issue
http://discuss.develop.com/archives/wa.exe...;T=0&P=7389

P.S.: Now that I look at the picture again I could have seen at the Green CPU load level that the load is just nice load... well... ok... stupidity happens.

ImmortalZ · Post by **ImmortalZ** » Sat Jul 15, 2006 12:31 pm

Umm, so you solved your proble? Or what? /blink.gif" style="vertical-align:middle" emoid=":o" border="0" alt="blink.gif" /> :genuinely confused:

BTW, the authority on and supreme overlord of ASGS is teh Pook, so I guess he'll answer this shortly /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Flower · Post by **Flower** » Sat Jul 15, 2006 1:31 pm

ImmortalZ wrote:QUOTE (ImmortalZ @ Jul 15 2006, 02:31 PM) Umm, so you solved your proble? Or what? /blink.gif" style="vertical-align:middle" emoid=":o" border="0" alt="blink.gif" /> :genuinely confused:

BTW, the authority on and supreme overlord of ASGS is teh Pook, so I guess he'll answer this shortly /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

Well no, my main Allegiance problem of too few FPS in heated situations is still present, but this post had nothing to do with it.

I just noticed that the ASGS Client needlessly gobbles CPU cycles. As I am not on a notebook this does not really bother me. But gobbling Cycles is certainly is not supposed to happen.

I just wanted to let you all know that there might be something of a small bug in ASGS (well or more likely in .NET, but as they wont fix it in time one will try to do a workaround in the client and so on)

Post by **Pook** » Sat Jul 15, 2006 2:19 pm

When Allegiance isn't running ASGS isn't doing anything.

When Allegiance IS running IT takes 100% CPU load.

I'm going to guess that the tools you're using are showing the Allegiance.exe process as an ASGS process, since ASGS is controlling the Allegiance.exe process.

Flower · Post by **Flower** » Sat Jul 15, 2006 2:39 pm

Pook wrote:QUOTE (Pook @ Jul 15 2006, 04:19 PM) When Allegiance isn't running ASGS isn't doing anything.

Yes exactly that is why I wondered why it still claims 100% Cpu.
If Allegiance were running I would not wonder this :-)

Allegiance was not running at the point of time when this screenshot was taken. I quit Allegiance, ASGS succeeded to log off. And about 5 minutes later while surfing the forums I noticed that the processor load is still at 100%. That caused me to look for the cause. If Allegiance is running I see it as Allegiance.exe.

But anyway it does not really seem to be a major problem just a weird occurence.
I think it would be interesting if other users experience it. (thats why I posted) After all it is easy to miss it as ASGS produces only nice CPU load.

I think I will beign to check my taskmanager everytime after I ran Allegiance too see I can determine a pattern.

Edit: Just created two more screenshots which are perhaps interesting:

http://static.flickr.com/57/190047751_a6d7b1c9a8_o.jpg
This one shows the processes while Allegiance and ASGSClient are both running.
In the beginning I am on the desktop and Allegiance is minimized.
Note the sharp increase in Allegiance.exe's CPU cycles as I switched to Alleg and flew a bit around in the training mission. Simultaneously ASGS "makes way" for Allegiance so that it can perform unhindered.
So far so good. It is a behavior that I as a user do judge as perfectly normal.

http://static.flickr.com/68/190047812_c7a68fd6c8_o.jpg
As one can see, I have closed Allegiance now. (using escape and the exit allegiance)
ASGS Client's CPU load drops as allegiance is closed and it logs out of ASGS.
But the suddenly (without relogin or allegiance running) the CPU load climbs again.
That is the behavior that I found curious.

Edit2:
While performing one of the trial runs I noticed that the CPU Cycle gobbling does already begin before I even log into Allegiance. (had ASGSClient closed and sarted it up again, jumped to 100% CPU at once) So one of my thoughts that it might have been an unloaded part of Alleg go yonder into the trash as well. (lets reboot and try again.. to make absolutely sure)

Edit3:
Well the reboot did indeed remove the problem for some time. But as this is not the first instance that I notice this I am quite sure it will return. I just need to find some pattern as to why it happens. (Guess it will only show if I either connect to a server or play for a longer time)

*sigh* I have a foreboding feeling that this is a needle in the haystack thing. :-/
Let us just see what happens after all Alleg still runs and thus I am not at risk regarding Alleg. withdrawal symptoms.

Edit4:
Gee it seems I might have found a pattern only a very strange on... I do not believe it completely yet and certainly do need to do some more test. The idle cpu problem does only happen if I start ASGSClient /while/ Teamspeak is running. Strange aye? But if I start it before I do start Teamspeak it behaves normally... *bonk* sometimes I have this urge to give windows a good kick in its kernel.
Will try to see if I can reproduce this behavior consistently. Mayhap reinstall Teamspeak and so on...

Flower · Post by **Flower** » Sun Jul 16, 2006 4:47 am

It seems that my above hypothesis that Teamspeak did interfere with the ASGS Client is likely correct.
Everytime I start the ASGS client "after" Teamspeak. The above described issue occurs.
When I start ASGS before Teamspeak the issue does not occur.

Abyss · Post by **Abyss** » Mon Aug 14, 2006 3:26 am

Flower wrote:QUOTE (Flower @ Jul 15 2006, 09:47 PM) It seems that my above hypothesis that Teamspeak did interfere with the ASGS Client is likely correct.
Everytime I start the ASGS client "after" Teamspeak. The above described issue occurs.
When I start ASGS before Teamspeak the issue does not occur.

I noticed ASGS using max cpu also when just sitting at the login prompt. Flower's observation about starting ASGS and Teamspeak holds true for me too.