Praney Behl 314 Posted August 31, 2011 Report Share Posted August 31, 2011 Hi fellows, Some of you may know me and others may not as I see a few new faces around here everyday. Its good to see the community is growing steadily, thanks to all the support and the amazing work by Seth & company and to Ubot Dev team. I must say I am again loving the coding experience with the mighty UbotStudio 4.x with remarkable power to take web automation to new heights. I have recently been working on changing over few of my bots to the new UbotStudio 4.x. I have also been trying to play around with Multi-threading(MT) in UbotStudio 4.x. I must say it works like a charm and I am really enjoying it. However, the great experience with MT, as we all know Ubot 4 is still in its Beta stage, but very close to being released. I including few other member have noticed, when they code and use MT in Ubot4 with "in new browser" browser windows, even after the script is stopped there are few orphan instances of "UBotBrowser.exe" lying around and holding a little bit of useful memory space. I had a chance to discuss the problem with Eddie from the Ubot Dev team, and the bug was recognized. He pointed the complexity in threading may take a longer time to officially fix the bug, and inspired me to create an external script to solve the issue temporarily. So cutting short on the story, I have put together a VBSCRIPT to un-officially solve the problem with stranded "UBotBrowser.exe" processes as a result of using Multi-threading in UbotStudio 4. Its working fine do kill the unwanted instances of the "UBotBrowser.exe" processes. Here is the script, I couldn't upload it as a .vbs so you may need to save it as a .vbs file and it can be called from the shell command. strComputer = "." strProcessToKill = "UBotBrowser.exe" SET objWMIService = GETOBJECT("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" _ & strComputer & "\root\cimv2") SET colProcess = objWMIService.ExecQuery _ ("Select * from Win32_Process Where Name = '" & strProcessToKill & "'") count = 0 FOR EACH objProcess in colProcess If objProcess.WorkingSetSize < 1048576 Then objProcess.Terminate() End If NEXT Special thanks to Eddie for the help and tips. If this helps you please feel free to say thanks, or any comments as you may have. Enjoy! Praney Behl 3 Quote Link to post Share on other sites
Bob The Builder 62 Posted August 31, 2011 Report Share Posted August 31, 2011 Hi fellows, Some of you may know me and others may not as I see a few new faces around here everyday. Its good to see the community is growing steadily, thanks to all the support and the amazing work by Seth & company and to Ubot Dev team. I must say I am again loving the coding experience with the mighty UbotStudio 4.x with remarkable power to take web automation to new heights. I have recently been working on changing over few of my bots to the new UbotStudio 4.x. I have also been trying to play around with Multi-threading(MT) in UbotStudio 4.x. I must say it works like a charm and I am really enjoying it. However, the great experience with MT, as we all know Ubot 4 is still in its Beta stage, but very close to being released. I including few other member have noticed, when they code and use MT in Ubot4 with "in new browser" browser windows, even after the script is stopped there are few orphan instances of "UBotBrowser.exe" lying around and holding a little bit of useful memory space. I had a chance to discuss the problem with Eddie from the Ubot Dev team, and the bug was recognized. He pointed the complexity in threading may take a longer time to officially fix the bug, and inspired me to create an external script to solve the issue temporarily. So cutting short on the story, I have put together a VBSCRIPT to un-officially solve the problem with stranded "UBotBrowser.exe" processes as a result of using Multi-threading in UbotStudio 4. Its working fine do kill the unwanted instances of the "UBotBrowser.exe" processes. Here is the script, I couldn't upload it as a .vbs so you may need to save it as a .vbs file and it can be called from the shell command. strComputer = "." strProcessToKill = "UBotBrowser.exe" SET objWMIService = GETOBJECT("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" _ & strComputer & "\root\cimv2") SET colProcess = objWMIService.ExecQuery _ ("Select * from Win32_Process Where Name = '" & strProcessToKill & "'") count = 0 FOR EACH objProcess in colProcess If objProcess.WorkingSetSize < 1048576 Then objProcess.Terminate() End If NEXT Special thanks to Eddie for the help and tips. If this helps you please feel free to say thanks, or any comments as you may have. Enjoy! Praney Behl 4.0.52 seems to help this a lot. I am going to do some more testing, but it looks like the problem bots I was see it with, have been resolved. Quote Link to post Share on other sites
Praney Behl 314 Posted August 31, 2011 Author Report Share Posted August 31, 2011 That is good news. I am gonna compile my bot into it now and report if any bugs.Don't have to put up with a stupid VBScript code. haha Quote Link to post Share on other sites
Bob The Builder 62 Posted September 2, 2011 Report Share Posted September 2, 2011 That is good news. I am gonna compile my bot into it now and report if any bugs.Don't have to put up with a stupid VBScript code. haha Let us know if you still see this, it seems almost completely fixed here. Quote Link to post Share on other sites
Praney Behl 314 Posted September 2, 2011 Author Report Share Posted September 2, 2011 Let us know if you still see this, it seems almost completely fixed here. I am going to test it now and see if it is fixed, to confirm. Quote Link to post Share on other sites
Praney Behl 314 Posted September 2, 2011 Author Report Share Posted September 2, 2011 It does seem like the issue is fixed. didn't had stranded instances after stop. Sweeeet! Quote Link to post Share on other sites
Bob The Builder 62 Posted September 2, 2011 Report Share Posted September 2, 2011 It does seem like the issue is fixed. didn't had stranded instances after stop. Sweeeet! I tested pretty aggressively running 100 processes at once and it worked like a champ Quote Link to post Share on other sites
Praney Behl 314 Posted September 2, 2011 Author Report Share Posted September 2, 2011 Yes, I am going to hit hard by the weekend, getting a memory upgrade to 16Gig, see how the puppy scales... Quote Link to post Share on other sites
Bob The Builder 62 Posted September 2, 2011 Report Share Posted September 2, 2011 Yes, I am going to hit hard by the weekend, getting a memory upgrade to 16Gig, see how the puppy scales... Got 12g, and 18ghz water cooled, CPU more of an issue, it spikes hard but could be werfault.exe issue I just reported. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.