Employee
•
547 Messages
I'm seeing CPU growth on version 8.1.0.3002
by bstern@us.ibm.com » Wed Jun 02, 2010 9:50 am
I am running the AT&T Network Client on my Windows 7 Ultimate 64-bit OS. I installed version 8.1.0.3002. I'm seeing a steady increase in process utilization for the netclient.exe process until it starts consuming 100% of one CPU core. This occurs after running for just a few hours.
I've been searching online and can't find anything that mentions CPU growth with version 8.1.0.3002.
any ideas?
I've been searching online and can't find anything that mentions CPU growth with version 8.1.0.3002.
any ideas?
*I am an AT&T employee, and the postings on this site are my own and don't necessarily represent AT&T's position, strategies or opinions.
© 2024 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T intellectual property and/or AT&T affiliated companies. All other marks are the property of their respective owners.
NancyKnows
Employee
•
547 Messages
13 years ago
by obrion » Mon Jun 28, 2010 3:04 pm
Robert
0
0
NancyKnows
Employee
•
547 Messages
13 years ago
by bstern@us.ibm.com » Tue Jun 29, 2010 6:57 pm
0
0
NancyKnows
Employee
•
547 Messages
13 years ago
by jonesn » Wed Jun 30, 2010 2:40 am
It would be useful to try to reduce this as it's just a waste of resource
This is the cpu consuming thread:
wow64win.dll+0x3fc2a
wow64win.dll+0x1ac48
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x24
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!RtlUniform+0x173
ntdll.dll!RtlResetRtlTranslations+0xd44
ntdll.dll!LdrInitializeThunk+0xe
USER32.dll!GetFocus+0x22
mfc90.dll+0x9a685
mfc90.dll+0x6717d
NetClient.exe+0x24484
ntdll.dll!RtlInitializeExceptionChain+0x63
ntdll.dll!RtlInitializeExceptionChain+0x36
0
0
NancyKnows
Employee
•
547 Messages
13 years ago
by bstern@us.ibm.com » Wed Jul 07, 2010 12:18 pm
0
0
NancyKnows
Employee
•
547 Messages
13 years ago
by bstern@us.ibm.com » Sat Jul 10, 2010 10:25 am
Here is what I did. I used a program called Process Explorer. I was able to see that NetClient was using SwiApiMux.exe. This seems to be related to Sierra Wireless. I compared my Windows 7 64-bit system with a machine that is very similar, but didn't have the Sierra Wireless drivers installed. I noticed that SwiApiMux.exe was NOT being used by NetClient.
Ultimately, I removed the Sierra Wireless drivers. I also went through the filesystem and removed all remnants of Sierra Wireless. Then I reinstalled AT&T Net Client and everything is working well.
0
0
NancyKnows
Employee
•
547 Messages
13 years ago
by jonesn » Mon Jul 26, 2010 3:32 am
However the 5-10% "leak" with no/low VPN activity and a minimize GUI is a seemingly unnecessary hit on system resource.
Can this be addressed?
Under windows is there a way of connecting without using the GUI?
0
0
NancyKnows
Employee
•
547 Messages
13 years ago
by jonesn » Tue Oct 05, 2010 10:31 am
0
0