| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Suggestions / Feedback
Thread: Bug: Exit Grid Agent causus ud.exe to consume 99% CPU |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 19
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
When my Pc starts, A tray icon for Word Community Grid Agent appears. If I invoke the context menu and choose Exit, my Pc becomes very irresponsive. If I look in my Task Manager's process list, I see UD.exe consuming 99% CPU most of the time. In contrast to WCGrid_rosetta.exe and ud_1582756.exe, which run at Priorit Low, ud.exe runs at priority Normal!
I would like the program to exit completely and certainly not this behaviour. I tried to check my version, but I can not find much information. The file version of ud.exe is 3.0.0.2844. |
||
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges: 
|
When UD.exe uses 100% of the cpu, this is usually a sign that it is preparing (including compressing) the results for sending them back to the server. This can take several minutes. If you see this happening for longer than 10 - 15 minutes, then something might be wrong. What happens if you let it run for a while?
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I will try this now and see what is happening in the morning. It would be quite a coincidence if that happened repeatedly at the moment I tried to Exit the program. Also, I do not like the fact that this compression is done at Normal process priority. I'll publish the results.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well, the UD.exe has been running all night. The total CPU time it has consumed is 16 hours and 20 minutes, which means that indeed it has been running at about 99% all the time.
In more detail: If the grid is running, there is a process WCGrid_rosetta.exe, that runs at priorit Low. If I choose exit form the system tray icon, this process disappears and a process ud_1582756.exe runs for about 3 seconds, also at priority Low. Thats also exits and ud.exe is started and takes all CPU time. Also, the current task progress is 63%, so I don't think results are to be send at this moment. If there is anything I can do to help analyze this program further, please feel free to contact me. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Blank mind. . . .
Well, that is certainly not the way that ud.exe is supposed to work. Exit is supposed to shut everything down, including ud.exe. This is the first time I have ever heard of a problem like this. So something has gone wrong with your software. As I see it, you have 2 real alternatives. The first is to wait for a staff member like Viktors to respond again. The second is to use Task Manager to stop ud.exe and then to uninstall. If something has gone wrong with the Agent that is supposed to send back the results from Rosetta, then there is no special reason to delay. If you uninstall, as I would in this case, then you can reboot to clean up any problems and reinstall from http://www.worldcommunitygrid.org , being careful to check the 'Previous member' box and sign in, giving your computer a new name [add 1 or 2 to the name]. Your local Agent will start out with 0 points but your points on the website will start out where you left off. I know it seems drastic, but if something has corrupted your software, then this is really the simplest fix. Please let us know what you decide. mycrofth |
|||
|
||||
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges:
|
After you exit the agent and the ud_nnnn.exe process ends, try using the task manager to stop the running UD.exe that you see running for a long time. See if you have another file called ud.exe somewhere else on your system besides in the WorldCommunityInstall directory. Also, have you registered this as a service or done some other cusomization? Does it still do this when you reboot? Have you scanned your system for viruses?
If you want me to see if results are being returned at the server end, please email me your device id number found on the preferences (check mark) window of your agent in question. Email to the support email for WorldCommunityGrid attn Viktors. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
1. The is no other UD.exe on the local system.
2. There is a good virusscanner running continuously. 3. I have done no customization, whatsoever. 4. It still happens after a reboot. 5. It does no happen on another system of mine. 6. I have found another application that keeps running at 99% after I quit it. 7. I used filemon to trace any file access by ud.exe, found none. 8. I used regmon to trace any registry access by ud.exe, found none. 9. I tried to hook into the process using the visual studio .NET debugger, but that failed. It kept informing me that it was busy loading the executable. 10. I uninstalled the WorldCommunityGrid, rebooted and installed it again. 11. My Device ID is 139722, for the fresh installation, I suppose. 12. Before I exited the last time, the tooltip said: "Primary task is executing (1% done)". I suppose it will not be sending any results at that time. The problem persists. Considering 5. and 6. I will blame my system for it and try to live with it. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
6. I have found another application that keeps running at 99% after I quit it. Yes, that sounds as though something (hopefully minor) has gone wrong on your system software. Really fixing that is time consuming and keeps me aggravated for most of a week, though I suppose some people get used to it. Enjoy your summer and merry crunching! mycrofth |
||
|
|
Alther
Former World Community Grid Tech United States of America Joined: Sep 30, 2004 Post Count: 414 Status: Offline Project Badges: 
|
6. I have found another application that keeps running at 99% after I quit it. Just out of curiosity, what's this other program? 9. I tried to hook into the process using the visual studio .NET debugger, but that failed. It kept informing me that it was busy loading the executable. That's interesting. If this is an NT based system (NT, 2000, XP), you should be able to attach to any process at any point. The fact that you can't implies that there is definitely something wrong...possibly hardware related, possibly a device driver...something running in ring 0 that's preventing the debugger from attaching. Are you able to attach the debugger to this other program that is also consuming 99% CPU?
Rick Alther
----------------------------------------Former World Community Grid Developer [Edit 1 times, last edit by Alther at Jun 29, 2005 11:11:42 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Let me just do some more testing, just for the sake of curiosity.
 Just out of curiosity, what's this other program? It is Toad (www.quest.com) a programming tool for Oracle. Are you able to attach the debugger to this other program that is also consuming 99% CPU? At first, I also got: --------------------------- Microsoft Development Environment --------------------------- Unable to break execution. Please wait until the debuggee has finished loading, and try again. --------------------------- Then, I attached to the process before it actually started to consume 99% CPU. That worked also for UD.exe! I than chose Exit in the systray on the Grid agent and waited for UD.exe to take over the CPU. Below, I show you the stack trace at an abritary breaktpoint of the execution (that is, when I chose to hit the "Break All" button). SetupHook.dll!66001328() kernel32.dll!7c809f12() SetupHook.dll!66002ef3() SetupHook.dll!66001b53() SetupHook.dll!66001a13() ntdll.dll!7c911993() ntdll.dll!7c911970() ntdll.dll!7c91056d() ntdll.dll!7c911993() ntdll.dll!7c911970() ntdll.dll!7c91056d() msvcrt.dll!77bfc2de() msvcrt.dll!77bfc2e3() kernel32.dll!7c80b810() ntdll.dll!7c90d592() kernel32.dll!7c809bbb() ole32.dll!774f20a9() SetupHook.dll!66004d0a() ntdll.dll!7c9011a7() ntdll.dll!7c923f31() ntdll.dll!7c910945() ntdll.dll!7c91094e() kernel32.dll!7c81ca3e() ntdll.dll!7c90dd87() kernel32.dll!7c81e0c2() ntdll.dll!7c919aeb() ntdll.dll!7c919ba0() kernel32.dll!7c80ac66() UD.EXE!005a2fe8() kernel32.dll!7c81caa2() ntdll.dll!7c919aeb() msvbvm60.dll!00b6a0d8() ntdll.dll!7c91056d() ws2_32.dll!71a31384() msvbvm60.dll!00b6a03b() kernel32.dll!7c8399f3() kernel32.dll!7c81cab6() UD.EXE!004e7694() kernel32.dll!7c809e2a() msvbvm60.dll!00bb239a() msvbvm60.dll!00bb1fb3() msvbvm60.dll!00bb22b4() msvbvm60.dll!00bb239a() msvbvm60.dll!00bb24fc() msvbvm60.dll!00bb271b() msvbvm60.dll!00bb28e7() msvbvm60.dll!00b7c4c9() msvbvm60.dll!00b69da4() msvbvm60.dll!00bae31d() msvbvm60.dll!00bb0300() msvbvm60.dll!00bc6ff5() msvbvm60.dll!00c28800() msvbvm60.dll!00c28879() UD.EXE!004f6017() I am not sure how attaching to this process has influenced the call stack, but calls into SetupHook.dll suggest there is some influence. Also, I set a breaktpoint on the deepest nesting of code running in UD.exe (UD.EXE!005a2fe8()) and waited for it to return to that point. Until now, after about 15 min, it has not returned to that address. I'll let it run on for a while. |
||
|
|
|