How can I connect to a network user process and manage it in vb.net?
Actually, I can only start a taskkill like this:
Process.Start("taskkill", "/S UC-PC109 /FI "USERNAME eq PC109" /PID 8324")
But I also need to check if program is executing and/or wait for program exit
for local processes....
Dim p As New Process()
Dim ps As New ProcessStartInfo
ps.FileName = "somefile.exe"
p.StartInfo = ps
p.Start()
p.WaitForExit()
You can use getprocesses to get them from a remote PC
https://msdn.microsoft.com/en-us/library/1f3ys1f9(v=vs.110).aspx
Process.GetProcessesByName(processName) will return all the processes that are running in system with this name. So you can fetch all the process using this method of Process Class like this
Process[] processes = Process.GetProcessesByName(processName);
Now if you have to terminate all the processes with this name then you can use bleow code
foreach (Process proc in processes)
{
try
{
proc.Kill();
}
catch (Exception exp)
{
//Log Exception.
}
}
or if you have to wait for any process then use this...
proc.WaitForExit(2000); //process is your process and 2000 is millisecond
Note: This code is written in C#, pls.
I set up a python code to run Selenium chromedriver.exe. At the end of the run I have browser.close() to close the instance. (browser = webdriver.Chrome()) I believe it should release chromedriver.exe from memory (I'm on Windows 7). However after each run there is one chromedriver.exe instance remain in the memory. I hope there is a way I can write something in python to kill the chromedriver.exe process. Obviously browser.close() doesn't do the work. Thanks.
per the Selenium API, you really should call browser.quit() as this method will close all windows and kills the process. You should still use browser.quit().
However: At my workplace, we've noticed a huge problem when trying to execute chromedriver tests in the Java platform, where the chromedriver.exe actually still exists even after using browser.quit(). To counter this, we created a batch file similar to this one below, that just forces closed the processes.
kill_chromedriver.bat
#echo off
rem just kills stray local chromedriver.exe instances.
rem useful if you are trying to clean your project, and your ide is complaining.
taskkill /im chromedriver.exe /f
Since chromedriver.exe is not a huge program and does not consume much memory, you shouldn't have to run this every time, but only when it presents a problem. For example when running Project->Clean in Eclipse.
browser.close() will close only the current chrome window.
browser.quit() should close all of the open windows, then exit webdriver.
Theoretically, calling browser.Quit will close all browser tabs and kill the process.
However, in my case I was not able to do that - since I running multiple tests in parallel, I didn't wanted to one test to close windows to others. Therefore, when my tests finish running, there are still many "chromedriver.exe" processes left running.
In order to overcome that, I wrote a simple cleanup code (C#):
Process[] chromeDriverProcesses = Process.GetProcessesByName("chromedriver");
foreach(var chromeDriverProcess in chromeDriverProcesses)
{
chromeDriverProcess.Kill();
}
//Calling close and then quit will kill the driver running process.
driver.close();
driver.quit();
I had success when using driver.close() before driver.quit(). I was previously only using driver.quit().
It's kinda strange but it works for me. I had the similar issue, after some digging I found that there was still a UI action going on in the browser (URL loading or so), when I hit WebDriver.Quit().
The solution for me (altough very nasty) was to add a Sleep() of 3 seconds before calling Quit().
This answer is how to properly dispose of the driver in C#
If you want to use a 'proper' mechanism that should be used to 'tidy up' after running ChromeDriver you should use IWebDriver.Dispose();
Performs application-defined tasks associated with freeing, releasing, or resetting unmanaged resources.
(Inherited from IDisposable.)
I usually implement IDisposable on class that is dealing with IWebDriver
public class WebDriverController : IDisposable
{
public IWebDriver Driver;
public void Dispose()
{
this.Driver.Dispose();
}
}
and use it like:
using (var controller = new WebDriverController())
{
//code goes here
}
Hope this saves you some time
Kill Multiple Processes From the Command Line
The first thing you’ll need to do is open up a command prompt, and then use the taskkill command with the following syntax:
taskkill /F /IM <processname.exe> /T
These parameters will forcibly kill any process matching the name of the executable that you specify. For instance, to kill all iexplore.exe processes, we’d use:
taskkill /F /IM iexplore.exe
So, you can use the following:
driver.close()
Close the browser (emulates hitting the close button)
driver.quit()
Quit the browser (emulates selecting the quit option)
driver.dispose()
Exit the browser (tries to close every tab, then quit)
However, if you are STILL running into issues with hanging instances (as I was), you might want to also kill the instance. In order to do that, you need the PID of the chrome instance.
import os
import signal
driver = webdriver.Chrome()
driver.get(('http://stackoverflow.com'))
def get_pid(passdriver):
chromepid = int(driver.service.process.pid)
return (chromepid)
def kill_chrome(thepid)
try:
os.kill(pid, signal.SIGTERM)
return 1
except:
return 0
print ("Loaded thing, now I'mah kill it!")
try:
driver.close()
driver.quit()
driver.dispose()
except:
pass
kill_chrome(chromepid)
If there's a chrome instance leftover after that, I'll eat my hat. :(
You should apply close before than quit
driver.close()
driver.quit()
Code c#
using System.Diagnostics;
using System.Management;
public void KillProcessAndChildren(string p_name)
{
ManagementObjectSearcher searcher = new ManagementObjectSearcher
("Select * From Win32_Process Where Name = '"+ p_name +"'");
ManagementObjectCollection moc = searcher.Get();
foreach (ManagementObject mo in moc)
{
try
{
KillProcessAndChildren(Convert.ToInt32(mo["ProcessID"]));
}
catch (ArgumentException)
{
break;
}
}
}
and this function
public void KillProcessAndChildren(int pid)
{
ManagementObjectSearcher searcher = new ManagementObjectSearcher
("Select * From Win32_Process Where ParentProcessID=" + pid);
ManagementObjectCollection moc = searcher.Get();
foreach (ManagementObject mo in moc)
{
try
{
KillProcessAndChildren(Convert.ToInt32(mo["ProcessID"]));
}
catch
{
break;
}
}
try
{
Process proc = Process.GetProcessById(pid);
proc.Kill();
}
catch (ArgumentException)
{
// Process already exited.
}
}
Calling
try
{
KillProcessAndChildren("chromedriver.exe");
}
catch
{
}
I had the same issue when running it in Python and I had to manually run 'killall' command to kill all processes. However when I implemented the driver using the Python context management protocol all processes were gone. It seems that Python interpreter does a really good job of cleaning things up.
Here is the implementation:
class Browser:
def __enter__(self):
self.options = webdriver.ChromeOptions()
self.options.add_argument('headless')
self.driver = webdriver.Chrome(chrome_options=self.options)
return self
def __exit__(self, exc_type, exc_val, exc_tb):
self.driver.close()
self.driver.quit()
And the usage:
with Browser() as browser:
browser.navigate_to_page()
Python code:
try:
# do my automated tasks
except:
pass
finally:
driver.close()
driver.quit()
I know this is somewhat of an old question, but I thought I'd share what worked for me. I was having problems with Eclipse -- it wouldn't kill the processes, and so I had a bunch of phantom processes hanging around after testing the code using the Eclipse runner.
My solution was to run Eclipse as administrator. That fixed it for me. Seems that Windows wasn't permitting Eclipse to close the process it spawned.
This work with python for me
import os
os.system('cmd /k "taskkill /F /IM chromedriver.exe /T"')
os.system('cmd /k "taskkill /F /IM chrome.exe /T"')
I have looked at all the responses and tested them all. I pretty much compiled them all into one as a 'Safety closure'. This in C#
Note: you can change the param from IModule app to that of the actual driver.
public class WebDriverCleaner
{
public static void CloseWebDriver(IModule app)
{
try
{
if (app?.GetDriver() != null)
{
app.GetDriver().Close();
Thread.Sleep(3000); // Gives time for everything to close before quiting
app.GetDriver().Quit();
app.GetDriver().Dispose();
KillProcessAndChildren("chromedriver.exe"); // One more to make sure we get rid of them chromedrivers.
}
}
catch (Exception e)
{
Console.WriteLine(e);
throw;
}
}
public static void KillProcessAndChildren(string p_name)
{
ManagementObjectSearcher searcher = new ManagementObjectSearcher
("Select * From Win32_Process Where Name = '" + p_name + "'");
ManagementObjectCollection moc = searcher.Get();
foreach (ManagementObject mo in moc)
{
try
{
KillProcessAndChildren(Convert.ToInt32(mo["ProcessID"]));
}
catch (ArgumentException)
{
break;
}
}
}
public static void KillProcessAndChildren(int pid)
{
ManagementObjectSearcher searcher = new ManagementObjectSearcher("Select * From Win32_Process Where ParentProcessID=" + pid);
ManagementObjectCollection moc = searcher.Get();
foreach (ManagementObject mo in moc)
{
try
{
KillProcessAndChildren(Convert.ToInt32(mo["ProcessID"]));
}
catch
{
break;
}
}
try
{
Process proc = Process.GetProcessById(pid);
proc.Kill();
}
catch (ArgumentException)
{
// Process already exited.
}
}
}
I have this issue. I suspect its due to the version of Serenity BDD and Selenium. The chromedriver process never releases until the entire test suite finishes. There are only 97 tests, but having 97 processes eat up the memory of a server that hasn't much resources may be having an affect on the performance.
To address I did 2 things (this is specific to windows).
before each test (annotated with #Before) get the process id (PID) of the chromedriver process with:
List<Integer> pids = new ArrayList<Integer>();
String out;
Process p = Runtime.getRuntime().exec("tasklist /FI \"IMAGENAME eq chromedriver.exe*\"");
BufferedReader input = new BufferedReader(new InputStreamReader(p.getInputStream()));
while ((out = input.readLine()) != null) {
String[] items = StringUtils.split(out, " ");
if (items.length > 1 && StringUtils.isNumeric(items[1])) {
pids.add(NumberUtils.toInt(items[1]));
}
}
after each test (annotated with #After) kill the PID with:
Runtime.getRuntime().exec("taskkill /F /PID " + pid);
For Ubuntu/Linux users: -
the command is either pkill or killall . pkill is generally recommended, since on some systems, killall will actually kill all processes.
I am using Protractor with directConnect. Disabling the "--no-sandbox" option fixed the issue for me.
// Capabilities to be passed to the webdriver instance.
capabilities: {
'directConnect': true,
'browserName': 'chrome',
chromeOptions: {
args: [
//"--headless",
//"--hide-scrollbars",
"--disable-software-rasterizer",
'--disable-dev-shm-usage',
//"--no-sandbox",
"incognito",
"--disable-gpu",
"--window-size=1920x1080"]
}
},
Make Sure You get the Driver instance as Singleton
then Apply at end
driver.close()
driver.quit()
Note: Now if we see task manager you will not find any driver or chrome process still hanging
I simply use in every test a method tearDown() as following and I have no problem at all.
#AfterTest
public void tearDown() {
driver.quit();
driver = null;
}
After quitting the driver instance clear it from the cache by driver = null
Hope the answer the question
There is another way which is working only for windows, but now it is deprecated. it works for previous selenium releases (it works on 3.11.0 version).
import org.openqa.selenium.os.WindowsUtils;
WindowsUtils.killByName("chromedriver.exe") // any process name you want
So, nothing worked for me. What I ended up doing was setting a unique ID on my addArguments to launch chromedriver, then when I want to quit I do something like this:
opts.addArguments(...args, 'custompid' + randomId());
Then to make sure it quits:
await this.driver.close()
await this.driver.quit()
spawn(`kill $(ps aux | grep ${RANDOM_PID_HERE} | grep -v "grep" | awk '{print $2}')`).on('error', e => { /* ignores when grep returns empty */ })
Ugly af, but it's the only thing that worked for my case.
just use this two ways:
open console and run this: taskkill /F /IM chromedriver.exe /T for kill all chrome processes
after how your test is complete you should driver.Dispose, not Close and also not Quit, just Dispose it.
Good Luck.
I came here initially thinking surely this would have been answered/resolved but after reading all the answers I was a bit surprised no one tried to call all three methods together:
try
{
blah
}
catch
{
blah
}
finally
{
driver.Close(); // Close the chrome window
driver.Quit(); // Close the console app that was used to kick off the chrome window
driver.Dispose(); // Close the chromedriver.exe
}
I was only here to look for answers and didn't intend to provide one. So the above solution is based on my experience only. I was using chrome driver in a C# console app and I was able to clean up the lingering processes only after calling all three methods together.
Observed on version 3.141.0:
If you initialize your ChromeDriver with just ChromeOptions, quit() will not close out chromedriver.exe.
ChromeOptions chromeOptions = new ChromeOptions();
ChromeDriver driver = new ChromeDriver(chromeOptions);
// .. do stuff ..
driver.quit()
If you create and pass in a ChromeDriverService, quit() will close chromedriver.exe out correctly.
ChromeDriverService driverService = ChromeDriverService.CreateDefaultService();
ChromeOptions chromeOptions = new ChromeOptions();
ChromeDriver driver = new ChromeDriver(driverService, chromeOptions);
// .. do stuff ..
driver.quit()
I have used the below in nightwatch.js in afterEach hooks.
afterEach: function(browser, done) {
// performing an async operation
setTimeout(function() {
// finished async duties
done();
browser.closeWindow();
browser.end();
}, 200);
}
.closeWindow() just simply closes the window. (But wont work for multiple windows opened).
Whereas .end() ends all the remaining chrome processes.
Please try this tested codes:
ChromeDriverService driverService = ChromeDriverService.createDefaultService();
ChromeDriver chrome = new ChromeDriver(driverService, chromeOptions);
//
// code
//
//
chrome.close();
chrome.quit();
driverService.close();
I'm calling a 3rd part app which 'sometimes' works in VB.NET (it's a self-hosted WCF). But sometimes the 3rd party app will hang forever, so I've added a 90-second timer to it. Problem is, how do I know if the thing timed out?
Code looks like this:
Dim MyProcess as System.Diagnostics.Process = System.Diagnostics.Process.Start(MyInfo)
MyProcess.WaitForExit(90000)
What I'd like to do is something like this
If MyProcess.ExceededTimeout Then
MyFunction = False
Else
MyFunction = True
End If
Any ideas?
Thanks,
Jason
There have been known issues in the past where apps would freeze when using WaitForExit.
You need to use
dim Output as String = MyProcess.StandardOutput.ReadToEnd()
before calling
MyProcess.WaitForExit(90000)
Refer to Microsoft's snippet:
// Start the child process.
Process p = new Process();
// Redirect the output stream of the child process.
p.StartInfo.UseShellExecute = false;
p.StartInfo.RedirectStandardOutput = true;
p.StartInfo.FileName = "Write500Lines.exe";
p.Start();
// Do not wait for the child process to exit before
// reading to the end of its redirected stream.
// p.WaitForExit();
// Read the output stream first and then wait.
string output = p.StandardOutput.ReadToEnd();
p.WaitForExit();
http://msdn.microsoft.com/en-us/library/system.diagnostics.process.standardoutput.aspx
Check the method return value - http://msdn.microsoft.com/en-us/library/ty0d8k56.aspx - if the call timed out, it will return False.
if(process.WaitForExit(timeout)) {
// user exited
} else {
// timeout (perhaps process.Kill();)
}
Async process start and wait for it to finish
I am writing a small app in VB and I would like to know how I would set it up so that when a user pressed a button, a sechduled task is ran. Keep in mind that this task is already created, I just need it to run.
Any ideas?
Thanks
Use the System.Diagnostics.Process class. You can create a process and run it with Process.Start() method.
EDIT:
Following code sample starts the helloworld.exe. This is just to give an idea about the Process class. You can find this example in Process.Start Method
using System;
using System.Diagnostics;
using System.ComponentModel;
namespace MyProcessSample
{
class MyProcess
{
public static void Main()
{
Process myProcess = new Process();
try
{
myProcess.StartInfo.UseShellExecute = false;
// You can start any process, HelloWorld is a do-nothing example.
myProcess.StartInfo.FileName = "C:\\HelloWorld.exe";
myProcess.StartInfo.CreateNoWindow = true;
myProcess.Start();
// This code assumes the process you are starting will terminate itself.
// Given that is is started without a window so you cannot terminate it
// on the desktop, it must terminate itself or you can do it programmatically
// from this application using the Kill method.
}
catch (Exception e)
{
Console.WriteLine(e.Message);
}
}
}
}
How about using the recently added System.Threading.Tasks library?
Link: http://msdn.microsoft.com/en-us/library/system.threading.tasks.aspx