Bonjour Leaking Handles?

I'm running Vista Ultimate x64, and the bonjour process (mdnsresponder.exe) has a ridiculous amount of outstanding handles open, at the moment.
There are nearly 60,000 open handles just in that process alone, which is more than all the rest of the 87 running processes on this computer put together.
It sure looks like Bonjour is leaking handles.
The handle count increases by one every few seconds, like clockwork.
The system has only been running for 49 hours, and it's already this bad. I'd hate to see it by next Tuesday, which will likely be the next time this system reboots.
What's going on with this?

Just an update...
I have not rebooted since my last post, and Bonjour is now happily holding on to 105,336 handles.
The leak continues...

Similar Messages

IE6 leaks "Handles" when calling *ANY* Java applet

Hello all IE experts,
It seems that IE has "Handles" leak when it calls Java Applet.
Every call to a Java method from JavaScript, IE allocate a handle and does
not free it.
THIS DOES NOT HAPPEN when I use mozilla or Netscape.
Versions:
* Windows 2000 SP 3 (The most recent, with all fixes of hfnetchk)
* Internet Explorer (The most recent one, with all fixes of hfnetchk)
Version 6.0.2800.1106
SP1
Q328970
Q324929
Q810847
Q813951
* Java Plug-in - 1.4.1_02-b06
If you compile the applet and use the test html, then press "Test" you will
notice that 1000 (or more) handles are allocated (At Windows Task Manager).
If you press again you will see that another 1000 (or more) handles are
allocated. The handles are NEVER released, even if you browse to other
sites. You can enjoy this process until there are no more handles to
allocate... :)
Notice that the applet I use does nothing... I've checked this with various
of applets on the web and the results are the same.
Can anyone help?
Best Regards,
Alon Bar-Lev
** The following html is used: (test1.htm)
<html>
<head>
<script LANGUAGE="JavaScript">
function OnTest () {
for (var i=0;i<1000;i++) { a1.method1 (); }
</script>
</head>
<body>
<input type=button onclick="OnTest ()" value="Test"></input>
<APPLET code="test1.applet1.class" archive="test1.jar" id="a1" name="a1">No
Java</APPLET>
</body>
</html>
** The following applet: (test1/applet1.java)
package test1;
import java.applet.*;
public class applet1 extends Applet {
public void method1 () {}
** The following makefile: (Makefile)
JAVAC="$(J2SE)\bin\javac" -classpath $(CLASSPATH)
JAR="$(J2SE)\bin\jar" -cvf
CLASSPATH=.
all:
$(JAVAC) test1/*.java
$(JAR) test1.jar test1/*.class

New information:
This happens from Java version 1.4.0_01.
This did not happen in Java version 1.4.0.
Alon.

Jvm unnamed windows events handle leak 1.3.1_08-b03 - 1.4.2-b28

Hello,
I have an server application that leaks windows unnamed event handles on small loads. (200 network connections) I've used the process explorer from www.sysinternals.com to find the type of handles that where leaking. I've run my application through jprobe several times and i'm not leaking any java objects. it doesn't happen on every run. It can run about 5 to 10 times with no leak but as i continue running a request that has 200 network connnections it will leak one handle. Over time they add up memory increases and eventually we get a out of memory error and the server has to be restarted
My application uses the following
java version "1.3.1_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_08-b03)
Java HotSpot(TM) Client VM (build 1.3.1_08-b03, mixed mode)
windows server 2000 service pack 3 (I've tried sp1 and sp2 same issue)
starting and stopping threads
inet jdbc driver una2000
zlib compression libraries
encryption DES
sockets
no jni code
My network code uses input.available() and Socket.setSoTimeout() I don't think the setSoTimeOut time is timing anything out on these small runs.
I've also have run it with
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
I've tried not stopping any threads from my thread pool and it made no change. It still leaks! :-(
Does anyone know what creates the unamed event handles? Are they created by synchronization? Since my applications uses so many different api's it's like looking for a needle in a hay stack.
p.s. I've been working on this problem on and off for about 1 month. I've search the java forums and google.
Thanks
Alexander Anguiano

My message has been here for a while and is off the first page. :-( Oh, well. I thought I would update this just incase anyone was following it. (can I award my self those duke dollars?)
I think i've found the problem of why we are leaking handles. In the first 10 minutes it leaked 3 handles.(they may not have leaked but are resource that our application needed because of all the lazy initialization that we do) I've been runing a 200 task request every 5 minutes for the last 6 hours and have not leak any handles. The problem appears to be with calls to socket.setSoTimeout. I set it to 0. This effectively tells the socket to never time out. This is not an acceptable solution to the problem. I will be working on that next.
Has any one had problems with the socket.setSoTimeout?
If not then it may have to do with our simulated select. We have one thread that handles connection. Once the connection is established it's put on a list that get's polled [input.available()] that is handled by thread 2 if there is data then it gets handled by a worker thread [thread n-12]. Once the worker thread has read up to 4K of data it is put back on thread 2. I'm thinking that it has to do with so many thread doing a little work on it.

Handle leaks?

Has anyone seen handle leaks in ODP.NET? I have a multi-threaded server application that contains managed and unmanaged C++ code and uses ODP.NET. It leaks handles that seem to be thread handles created by ODP.NET. I cannot reproduce it in a simple test. I am working on it, but it would be nice to know if anyone noticed the same problem and has a workaround or fix. This is a big problem in my app because the number of handles goes up to 10,000 in a couple of hours. GC.Collect does not help.
Thanks,
Aleksey

Yes, I know that. I do close and dispose everything. The behaviour is hard to reproduce, but it does happen.
One quick tip you can try is to explicitly close all
objects you created when no longer needed. For
example, call the Close/Dispose method on your your
ODP.NET connections, DataReaders, etc. objects before
you leave your applications scope. Sometimes the
.NET garbage collector cannot reclaim resources
quickly enough under heavily-loaded conditions.
Alex

Process ID doesn't seams to be reused

Hi,
I have a virtual machine hosted by Windows server 2008 HyperV, the virtual machine also runs windows server 2008.
In the task manager the process ID (PID) keeps increasing. The PID are in the 4 milions now! Is this something typical? I have others system with the same setup and they don't behave that way; the PID are at the most around 10000.
Thanks for help
Pierre

Hi Pierre,
Glad to hear that you had solved the issue.
Based on my research, High-value PID in task manager may indicates that some program at some stage probably created tens of thousands (or hundreds of thousands) of processes.
However, once the system has started to use high pids, it can continue to use them until rebooted, Although PID can be reused, it is more common to see the number increase.
High PIDs on their own don't usually cause a problem, but a program that leaks handles will eventually cause all sort of weird problems such as screens that can't draw themselves, programs won't open properly etc.
Reference from:
High values of Process ID in Task Manager
I hope this helps.

Java.util.zip.ZipException: Too many open files on Linux

Hi,
We have web application running on Caucho's resin server on jdk 1.5.0_11 and Red hat Linux. We are noticing that java process is running out of file handles within 24-30 hours. We have file limit of 5000 which it consumes in 24 hours throwing 'java.util.zip.ZipException: Too many open files'.
I have made sure all sorts of file handles are closed from application point of view. Here is the snapshot of lsof (list of file handles) from java process. The following list keeps growing until it runs out of limit. Do you have tips/suggestions on how to mitigate this problem (considering we dont want to increase ulimit for this process)? Also, can you make out any thing more from the description of file handles like, are they unclosed POP3 connections or URL connection to external sites?
java 7156 resin 120u IPv4 34930051 UDP localhost.localdomain:59693
java 7156 resin 121u IPv4 34927823 UDP localhost.localdomain:59663
java 7156 resin 122u IPv4 34931861 UDP localhost.localdomain:59739
java 7156 resin 123u IPv4 34932023 UDP localhost.localdomain:59745
java 7156 resin 124u IPv4 34930054 UDP localhost.localdomain:59700
java 7156 resin 125u IPv4 34927826 UDP localhost.localdomain:59665
java 7156 resin 126u IPv4 34927829 UDP localhost.localdomain:59666
java 7156 resin 127u IPv4 34930057 UDP localhost.localdomain:59703
java 7156 resin 128u IPv4 34930713 UDP localhost.localdomain:59727
java 7156 resin 129u IPv4 34930716 UDP localhost.localdomain:59730
java 7156 resin 130u IPv4 34932238 UDP localhost.localdomain:59789
java 7156 resin 131u IPv4 34932026 UDP localhost.localdomain:59749
java 7156 resin 132u IPv4 34932221 UDP localhost.localdomain:59770
java 7156 resin 133u IPv4 34932224 UDP localhost.localdomain:59775
java 7156 resin 134u IPv4 34932029 UDP localhost.localdomain:59753
java 7156 resin 135u IPv4 34932032 UDP localhost.localdomain:59754
java 7156 resin 138u IPv4 34932035 UDP localhost.localdomain:59760
java 7156 resin 139u IPv4 34932038 UDP localhost.localdomain:59763
java 7156 resin 140u IPv4 34932227 UDP localhost.localdomain:59780
java 7156 resin 141u IPv4 34932230 UDP localhost.localdomain:59781
java 7156 resin 144u IPv4 34932234 UDP localhost.localdomain:59786
java 7156 resin 146u IPv4 34932241 UDP localhost.localdomain:59792
java 7156 resin 147u IPv4 34932247 UDP localhost.localdomain:59802

Finally we resolved this issue. It was oracle driver which had some compatibility issue, we upgraded our Oracle client driver to newer version, and this fixed the problem. Base line, there was nothing wrong with application code, code was doing good resource clean up, but oracle driver was leaking handles per every connection.

ORA-12571

My programming just do some opertion of selecting and updating frequently.When the programme ran for 7-10days there occured ORA-12571 error first followed by several ORA-01041 errors.
Please help me! Very urgent...

ORA-12571 indicates a broken connection between the Oracle client and the server. This could be (as Justin points out) due to a temporary network glitch or due to the death of a server process. In either case, the client side marks the connection as broken and in this case has cleaned up the assosciated data structures. Further operations return ORA-1041 as as result.
The only option at this point is to reestablish the connection to the server from your application or restart the application. Check any kind of memory leak, handle leak, etc. especially when you have a long running process.

Open Files On Linux

Hi,
We are running WL 6.1 SP4 in a clustered environment....2 Quad CPU Sparc SUN boxes and one Quad CPU Intel box running Red Hat Linux (kernel 2.4.20) and have noticed that Linux has a LOT more open files than the Sun boxes (103281 for the Linux Box versus 2558 for the Solaris box). This seems to have the side affect of making the Linux box use lots more system CPU time compared to the SUN boxes.....my guess is that this is also not very efficient. Is there something that can be done to reduce the number of open files? We are using the Native I/O performance pack and the Sun 1.3.1_07 JVM.

Finally we resolved this issue. It was oracle driver which had some compatibility issue, we upgraded our Oracle client driver to newer version, and this fixed the problem. Base line, there was nothing wrong with application code, code was doing good resource clean up, but oracle driver was leaking handles per every connection.

Creative Cloud Leaks Thread Handles

I have Creative Cloud version 1.8.0.447 running on windows 7, and I notice that it leaks a Thread Handle, about 4 times, or so, per minute. Since I leave my computer on most of the time, after a few days, the number of leaked Thread Handles is up in the tens of thousands.
I can see the thread handles leaking using Process Explorer.
Generally when a thread ends, its handle needs to be closed, or else the handle will stay active forever, or until the process ends. It looks like the programming team is not closing these handles after the threads end.
Please, adobe, fix this problem in a future release of creative cloud.
-Todd

Some 10.9.x links
-next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
-Mac 10.9.4 and OpenCL issue https://forums.adobe.com/thread/1514717
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-and https://forums.adobe.com/thread/1507936
or
A chat session where an agent may remotely look inside your computer may help
Creative Cloud chat support (all Creative Cloud customer service issues)
http://helpx.adobe.com/x-productkb/global/service-ccm.html

Handle leak - Crystal for VS 2010

I've been playing with the Crystal VS2010 runtime and have come across a problem which I believe might be a handle-leak in Crystal Reports.
I can reproduce this at will using the following example:
I created a project with a typed dataset (containing 2 empty tables with only a single column each). I then added a blank report to the project and only added a single text object to it - no data is loaded from the dataset at all.
Then, I can execute the following 100 times in a loop:
using (DataSet1 dataSet = new DataSet1())
   using (CrystalReport1 report = new CrystalReport1())
      report.SetDataSource(dataSet);
      report.Close();
   dataSet.Clear();
This I then follow with a forced garbage collect, just to make sure everything was cleaned up properly. However, +- 100 new handles were opened and using sysinternals' handle.exe, these show up as Mutexes e.g.:
1324: Mutant        \Sessions\1\BaseNamedObjects\CrystalReportXalanInitilizeMutex2916l
I haven't been able to find any information about this on the forums or the internet - can anyone confirm if this is a known issue? (Or am I doing something stupid? )
Thanks!

Hi,
I've tried some of your suggestions:
In you report check on No Printer and check off all o f the Verify Database options. - Made no difference
Also, be sure to use the Legacy mode in your app.config file, search for it. MS issue with DataSets. - Also, no difference
GDI Objects - These don't budge - this is a Mutex leak, not a GDI leak
As for datasets, I'm not filling the dataset - its empty. So a database does not enter into the equation, and no database connection handles are therefore ever created.
Also, I tried the printer theory by running the app on a machine without any printers installed - the problem persisted. Machines also have entirely different graphics card drivers, so highly unlikely to cause the problem.
I've also tried targeting both Framework 4.0 and Framework 2.0 - the leak occurs in both cases.
The code that I posted was only a snippet yes, but it really is 90% of the test-app. This is the whole content of Form1.cs (a single-button form):
using System;
using System.Windows.Forms;
namespace CrystalLeakTest
    public partial class Form1 : Form
        public Form1()
            InitializeComponent();
        private void ProduceReport()
            using (DataSet1 dataSet = new DataSet1())
                using (CrystalReport1 report = new CrystalReport1())
                    report.SetDataSource(dataSet);
                    report.Close();
                dataSet.Clear();
        private void button2_Click(object sender, EventArgs e)
            for (int i = 0; i < 100; i++)
                ProduceReport();
            GC.Collect();
            GC.WaitForPendingFinalizers();
            GC.Collect();
            MessageBox.Show("Done");
The rest of the app is simply a blank report, a blank typed dataset (with 1 table and 1 column - no data). That really is it
Is there anything else I can try?
Thanks!

Token Handle Leak in RDPShell.exe on 2012 R2 (does not occur in 2008)

I have several Terminal Services farms running both 2008 and 2012 R2.
Only those farms running 2012 exhibit the problem of excessive token handles in RDPShell.exe
On 2008, the handle count is around 210 (a mix of Desktop, Directory, ETWRegistration, Event, File, Key, Mutant, Process, Section, Thread, WindowStation).
However, on 2012 R2 (running the same client application) RDPShell leaks Token handles (with handle counts in the thousands). The current maximum handle count for RDPShell on one RDS server is 7620 handles...
Example below taken from ProcessHacker:
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x7644
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x764c
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x7650
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x7654
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x7658
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x765c
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x7660
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x7664
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x7668
Token, CORPORATE\[LoggedOnUserName]: 0xda8e99c, 0x766c
I would like to raise this as a Connect bug, however cannot see how to raise bugs on Connect for any Windows Operating systems.
Is anyone else experiencing similar?

Hi Brett,
Thank you for posting in Windows Server Forum.
Can you let us know, with which application you are facing the leaking process?
There are certain scenario when you can face this error, which is occurring in server 2008 R2. You can check with
this article
for reference. According to that, it might occurs due to some allocated memory is not released correctly in the Rdpshell.exe process. Here you need to close all the running application and need to wait for some time and retry again to work back.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Adobe Reader X leaks GDI handles in quick search box

Just installed Adobe Reader X a couple of days ago (Windows 7, x64). I used it for numerous online documents (in Firefox), while searching for some specific terms in each document. After a while the reader presented a strange picture, not properly painting itself anymore. Then, the reader became unresponsive, and Firefox too, and I had to kill the task.
This happened a few times on different pdf documents.
In my programming career things like these have happened more often so, when the behavior happened again, I went checking the process using Windows Task Manager, adding a few extra columns (Handles, User Objects, GDI Objects) and found that the number of GDI objects was nearly 10000, the absolute limit that Windows imposes on any single process.
I went on checking the reader, now standalone and without Firefox, to see if the problem would persist. Opened a few pdfs and scrolled back and forth. No problems -
tried the same in Firefox to see if the plugin was OK - still no problem.
Then started using the quick search box (Ctrl-F) and repeatedly looked for something trivial (e.g. just a single letter A) - Bingo! Now the GDI handle count starts rising seriously, and does not come back to the original level.
This is definitely a leak, and it needs to be fixed.

We don't process bug reports via these forums - please post any details of unexpected behaviors to the official reporting form.

Registry handles leaked from

+
System
Provider
[ Name]
Microsoft-Windows-User Profiles Service
[ Guid]
{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}
[ EventSourceName]
profsvc
EventID
1530
[ Qualifiers]
32768
Version
0
Level
3
Task
0
Opcode
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2011-06-11T07:37:12.000Z
EventRecordID
127007
Correlation
Execution
[ ProcessID]
0
[ ThreadID]
0
Channel
Application
Computer
Panther-PC
Security
[ UserID]
S-1-5-18
EventData
Detail
16 user registry handles leaked from \Registry\User\S-1-5-21-1082989139-2594333343-3947924465-1001: Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001
Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001 Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft
shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001 Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001
Process 828 (\Device\HarddiskVolume1\Program Files\NVIDIA Corporation\nTune\nTuneService.exe) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001 Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows
Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Microsoft\SystemCertificates\My Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key
\REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Microsoft\SystemCertificates\CA Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Microsoft\SystemCertificates\Root
Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Microsoft\SystemCertificates\SmartCardRoot Process 2384 (\Device\HarddiskVolume1\Program
Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Microsoft\SystemCertificates\TrustedPeople Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft
shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Microsoft\SystemCertificates\trust Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE)
has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Policies\Microsoft\SystemCertificates Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Policies\Microsoft\SystemCertificates
Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Policies\Microsoft\SystemCertificates Process 2384 (\Device\HarddiskVolume1\Program
Files\Common Files\microsoft shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Policies\Microsoft\SystemCertificates Process 2384 (\Device\HarddiskVolume1\Program Files\Common Files\microsoft
shared\Windows Live\WLIDSVC.EXE) has opened key \REGISTRY\USER\S-1-5-21-1082989139-2594333343-3947924465-1001\Software\Microsoft\SystemCertificates\Disallowed
should i be worried or can i get some help with this ?

I'm having the same problem on one of work's Server 2008 R2 machines, but the software causing the leaks are the Microsoft Windows programs
cmd.exe
robocopy.exe
conhost.exe
Microsoft can you please stop your software from leaking, thank you.
From the event viewer
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
6 user registry handles leaked from \Registry\User\S-1-5-21-3799963273-679199981-738785089-500:
Process 2348 (\Device\HarddiskVolume2\Windows\System32\cmd.exe) has opened key \REGISTRY\USER\S-1-5-21-3799963273-679199981-738785089-500
Process 6532 (\Device\HarddiskVolume2\Windows\System32\Robocopy.exe) has opened key \REGISTRY\USER\S-1-5-21-3799963273-679199981-738785089-500
Process 2348 (\Device\HarddiskVolume2\Windows\System32\cmd.exe) has opened key \REGISTRY\USER\S-1-5-21-3799963273-679199981-738785089-500\Software\Microsoft\Windows NT\CurrentVersion
Process 2348 (\Device\HarddiskVolume2\Windows\System32\cmd.exe) has opened key \REGISTRY\USER\S-1-5-21-3799963273-679199981-738785089-500\Control Panel\International
Process 6700 (\Device\HarddiskVolume2\Windows\System32\conhost.exe) has opened key \REGISTRY\USER\S-1-5-21-3799963273-679199981-738785089-500\Control Panel\International
Process 6532 (\Device\HarddiskVolume2\Windows\System32\Robocopy.exe) has opened key \REGISTRY\USER\S-1-5-21-3799963273-679199981-738785089-500\Control Panel\International

Call executable handle leak

We noticed in TestStand 4.1 that when we use "Call Executable" on a batch file:
with "no wait" it leaks a handle on each call
with other view options thatn "show minimized" it leaks GDI objects
We can work around the first issue by using CloseHandle (from kernel32.dll) on RunState.PreviousStep.ProcessHandle, but I would like to know whether these are known issues and are addressed in later versions of TS.
Best regards
Peter

In later versions of TestStand, the default behavior of a new callexecuteable step is to NOT store the process handle at all (instead it gets closed immediately). There is a setting for whether or not to store the handle and an expression to specify where to store it as shown below:
For the GDI object leak, are you seeing a leak in the TestStand process or is the GDI object leaking because the handle hasn't been closed yet, so the other process is still around and still using GDI objects? Does the GDI leak go away if you close the process handle? If you call callexecutable in a tight loop does the number of GDI objects grow unbounded or does it level off (i.e. is it really a leak or a one-time allocation)?
-Doug

Handle leak when using ADO2.7 access oracle

Ado version:2.7
OS:Window2000 professional
Oracle Server:9.2.0.1.0
Client Provider:9.2.0.1.0
Using Oracle OLEDB connection oracle
when i execute such function in my test program continuously:
Handle count of the program will increase.I know handle will increase for connection pool ,but it will stop increasing when handle count reach one value. i think this is a problem that ADO cann't match with Oracle OLEDB
better.
Any suggestion?
Set mConOracle = New Connection
mConOracle.CursorLocation = adUseClient
mConOracle.ConnectionString = "Provider=OraOLEDB.Oracle.1;Password=123;Persist Security Info=True;User ID=abc;Data Source=aaa;OLE DB Services=-1; "
mConOracle.Open
mConOracle.Close
Set mConOracle=Nothing

Ok,
I tried out connection pooling switching on/off. Also waited some minutes for the pool timeout. But nothing happened.
So I made some further tests and this is what I found out:
- The left handles are all semaphores
- To generate a handle leak it is necessary to create an ADO object, call connect and do a database query. Actually some data must be transmitted over the network. Then close connection, release ADO object. -> 2-3 semaphore handles are left.
- Handle leak occurs indepentendly of apartment or multi threaded
- MDAC 2.7, MDAC 2.8 was used with no success
However, we hat one piece of software here, which didn't have handle leaks. So I did some more investigation on that phenomena.
This is what happened and could be used as a workaround until a fix is available:
- I recognized, that if at least one connection (which has been really established once by the underlying components) has been opened and is kept open, it is possible to create more ADO objects, use them for database retrieval and release them again without having the handle count increased.
- So the handle leak seems only to occur, if there is no more database connection in use and one of the underlying components tries to release everything. Each time this happens 2-3 semaphore handle are left.
- Finally my current workaround is to create and open on initalization of my process an ADO object and the database connection and leave this object alone without touching it again until the process ends. For every database query in any thread I can now use a new ADO object, without having the handles increased and never released.
So, this is the end for now. I hope this information can help somebody to figure out where the problem is eventually located and a fix could be released.
Hopefully,
Markus (writing under Uwes account)

Bonjour Leaking Handles?

Similar Messages

Maybe you are looking for