Hi,
Ever since I've started to use MJ I'm experiencing handles leak on my Win32 XP SP3 + latest patches Dell XPS M1210.
The handle count starts at about 20K and grows beyond 30K with the same set of applications.
Through process monitor I can see that the growth is in the System (not application process), and it looks like the handle leak is from opening of HKLM registry entries.
It gets especially bad at night.
I ran a manual MJ SW update and saw the handle count jump by some 3K.
Anyone else sees this?
Thx,
D
MJ has handles leak?
Moderators: Bill Smith, Pilot
After more checking, there's definitely a handle leak in MJ. Here's how you can see it:
1.Install Sysinternals' Process Explorer (if you haven't already).
2.Open Process Expolrer
3.View|Select Columns, Handles tab, check all
4.View|Show Unnamed Handles and Mappings
5.Click Ctrl-L to show lower pane
6.Click Ctrl-H to put Handles View in the lower pane
7.Click on Handles column to sort process according to their handles count and sort them in descending order. The System process would be at the top.
8.Write down the handles count of the System process
9.Pick up the handset and watch handles count - it'd increase
10.Hangup and watch the count - it'd decrease, but would not go back to the initial value
1.Install Sysinternals' Process Explorer (if you haven't already).
2.Open Process Expolrer
3.View|Select Columns, Handles tab, check all
4.View|Show Unnamed Handles and Mappings
5.Click Ctrl-L to show lower pane
6.Click Ctrl-H to put Handles View in the lower pane
7.Click on Handles column to sort process according to their handles count and sort them in descending order. The System process would be at the top.
8.Write down the handles count of the System process
9.Pick up the handset and watch handles count - it'd increase
10.Hangup and watch the count - it'd decrease, but would not go back to the initial value
Re: MJ has handles leak?
huh? Handlesleak? wtf is that?
I think that's why some of you uber-geeks have trouble using the thing. You play with the computer to friggin much, lol. Mine has worked on 3 different computer and two different os's without a hitch and I have no idea what the heck a "handle" is or if it's leaking ot not and don't care.
I think that's why some of you uber-geeks have trouble using the thing. You play with the computer to friggin much, lol. Mine has worked on 3 different computer and two different os's without a hitch and I have no idea what the heck a "handle" is or if it's leaking ot not and don't care.
qwer1304 wrote:Hi,
Ever since I've started to use MJ I'm experiencing handles leak on my Win32 XP SP3 + latest patches Dell XPS M1210.
The handle count starts at about 20K and grows beyond 30K with the same set of applications.
Through process monitor I can see that the growth is in the System (not application process), and it looks like the handle leak is from opening of HKLM registry entries.
It gets especially bad at night.
I ran a manual MJ SW update and saw the handle count jump by some 3K.
Anyone else sees this?
Thx,
D
Re: MJ has handles leak?
Wow, that is a piss poor stance to take on what is basically a electronics support and modification forum.Azorix wrote:huh? Handlesleak? wtf is that?
I think that's why some of you uber-geeks have trouble using the thing. You play with the computer to friggin much, lol. Mine has worked on 3 different computer and two different os's without a hitch and I have no idea what the heck a "handle" is or if it's leaking ot not and don't care.
If its working for you great... but if thats as far as you want to get into it I'd suggest staying in the shallow end.
Edit: I might as well answer the question at the top of your post.
From wikipedia's explanation:
Code: Select all
A handle leak is a type of software bug that occurs when a computer program asks for a handle to a resource but does not free the handle when it is no longer used. If this occurs frequently or repeatedly over an extended period of time, a large number of handles may be marked in-use and thus unavailable, causing performance problems or a crash.
The term is derived from memory leak.Ah something I know about!
MJ has been very stable on "handles", in the low 600's for the actual count. I leave it run all day and there has been no increase (aka leak).
I think you have some other process with a problem.
In addition to the one another posted mentioned, a faboulous utility is TaskInfo:
http://www.iarsn.com/taskinfo.html
It will show you the handles count for each process, and you can watch for the one that is increasing and eating you up, etc.
MJ has been very stable on "handles", in the low 600's for the actual count. I leave it run all day and there has been no increase (aka leak).
I think you have some other process with a problem.
In addition to the one another posted mentioned, a faboulous utility is TaskInfo:
http://www.iarsn.com/taskinfo.html
It will show you the handles count for each process, and you can watch for the one that is increasing and eating you up, etc.
I know that the MJ process doesn't leak. The thing is that MJ leaks handles NOT in the MJ process, but in some driver. Drivers are associated with the System process.jonpod wrote:MJ has been very stable on "handles", in the low 600's for the actual count. I leave it run all day and there has been no increase (aka leak).
I think you have some other process with a problem.
If you go off-hook and then on-hook and watch the handles count for the System process, you will see that the number of handles grows every time you do the sequence by several hundreds.