R
Rich G
I have a system-wide problem where the action of right-clicking on
files creates handles to their directory that are never released. I'm
running Windows XP with the latest official updates and am monitoring
handles with Process Explorer. I have a dual-boot system with Win 98
on another partition.
Here's an example of the problem.
When I use Windows Explorer to open to C:\Parent\Child, Process
Explorer reports the creation of the following handle: C:\Parent\Child
OK, so far, so good.
Then let's say I then select 5 files in C:\Parent\Child. Process
Explorer reports no new handles. OK, sounds fine.
Then I right-click the 5 files, bringing up the context menu. Process
Explorer reports 5 new handles, each one the same, namely:
C:\Parent\Child\ (note, for what it's worth, there is a final
backslash that makes these handles different from the one created when
C:\Parent\Child is opened).
Then let's say I simply choose nothing from the context menu and
instead go up a directory to C:\Parent. Process Explorer shows that
the initial handle C:\Parent\Child is eliminated. HOWEVER, all 5 of
the C:\Parent\Child\ handles remain. And they never die naturally.
In fact, after right-clicking the files, the handles remain no matter
whether I choose a menu option, hit esape, change the directory, or do
anything else. The handles are there to stay. *In short, it is the
action of right-clicking the files that creates the undying handles.*
The problem is not limited to Windows Explorer. It seems to be
system-wide. For example, a very similar thing happens when I use
2xExplorer. The only difference from the above example is that two
handles are created (to 2xExplorer) when I initially open
C:\Parent\Child, but both of those handles disappear after I exit the
directory. Otherwise, the handle misbehavior is identical, i.e., there
remain as many handles called C:\Parent\Child\ as there were files in
C:\Parent\Child that were right-clicked. Likewise, right-clicking
files within an MS Word file dialogue box produces similar handle
problems.
I can kill these handles from within Process Explorer or shut down
explorer.exe (or 2xExplorer, or Word, etc.). These work-arounds work
just fine for me.
Nonetheless, this problem has been more than a little annoying. I've
done a fair amount of web research to try to find the answer, but no
dice. In short, I'm in way over my head and I would be very grateful
if one of you could help. Many thanks in advance.
-Rich
files creates handles to their directory that are never released. I'm
running Windows XP with the latest official updates and am monitoring
handles with Process Explorer. I have a dual-boot system with Win 98
on another partition.
Here's an example of the problem.
When I use Windows Explorer to open to C:\Parent\Child, Process
Explorer reports the creation of the following handle: C:\Parent\Child
OK, so far, so good.
Then let's say I then select 5 files in C:\Parent\Child. Process
Explorer reports no new handles. OK, sounds fine.
Then I right-click the 5 files, bringing up the context menu. Process
Explorer reports 5 new handles, each one the same, namely:
C:\Parent\Child\ (note, for what it's worth, there is a final
backslash that makes these handles different from the one created when
C:\Parent\Child is opened).
Then let's say I simply choose nothing from the context menu and
instead go up a directory to C:\Parent. Process Explorer shows that
the initial handle C:\Parent\Child is eliminated. HOWEVER, all 5 of
the C:\Parent\Child\ handles remain. And they never die naturally.
In fact, after right-clicking the files, the handles remain no matter
whether I choose a menu option, hit esape, change the directory, or do
anything else. The handles are there to stay. *In short, it is the
action of right-clicking the files that creates the undying handles.*
The problem is not limited to Windows Explorer. It seems to be
system-wide. For example, a very similar thing happens when I use
2xExplorer. The only difference from the above example is that two
handles are created (to 2xExplorer) when I initially open
C:\Parent\Child, but both of those handles disappear after I exit the
directory. Otherwise, the handle misbehavior is identical, i.e., there
remain as many handles called C:\Parent\Child\ as there were files in
C:\Parent\Child that were right-clicked. Likewise, right-clicking
files within an MS Word file dialogue box produces similar handle
problems.
I can kill these handles from within Process Explorer or shut down
explorer.exe (or 2xExplorer, or Word, etc.). These work-arounds work
just fine for me.
Nonetheless, this problem has been more than a little annoying. I've
done a fair amount of web research to try to find the answer, but no
dice. In short, I'm in way over my head and I would be very grateful
if one of you could help. Many thanks in advance.
-Rich