Objects ready for finalization are being blocked
0
Whenever someone tries to access my application, if more than one person is using it it starts to hang. I recreated the issue and ran DebugDiag memory check and get this warning.
Number of objects ready for finalization: 457779
It then tells me that the finalizer thread may be blocked.
As the number of finalizable objects is more than 0, please check the finalizer thread to see if it is blocked or active
Finalizer Thread
ntdll!NtWaitForSingleObject+14
KERNELBASE!WaitForSingleObjectEx+8f
clr!CLREventBase::WaitEx+17c
clr!CLREventBase::WaitEx+113
clr!CLREventBase::WaitEx+7c
clr!FinalizerThread::WaitForFinalizerEvent+44
clr!FinalizerThread::FinalizerThreadWorker+54
clr!Frame::Push+59
clr!FillInRegTypeMap+198
clr!FillInRegTypeMap+c1
[[DebuggerU2MCatchHandlerFrame]]
clr!FinalizerThread::FinalizerThreadStart+10a
clr!Thread::intermediateThreadProc+86
kernel32!BaseThreadInitThunk+14
ntdll!RtlUserThreadStart+21
Any idea what might be going on?
c# asp.net-mvc memory-leaks
asked Jan 2 at 19:15
TheDizzleTheDizzle
56921131
|
show 2 more comments
0
Whenever someone tries to access my application, if more than one person is using it it starts to hang. I recreated the issue and ran DebugDiag memory check and get this warning.
Number of objects ready for finalization: 457779
It then tells me that the finalizer thread may be blocked.
As the number of finalizable objects is more than 0, please check the finalizer thread to see if it is blocked or active
Finalizer Thread
ntdll!NtWaitForSingleObject+14
KERNELBASE!WaitForSingleObjectEx+8f
clr!CLREventBase::WaitEx+17c
clr!CLREventBase::WaitEx+113
clr!CLREventBase::WaitEx+7c
clr!FinalizerThread::WaitForFinalizerEvent+44
clr!FinalizerThread::FinalizerThreadWorker+54
clr!Frame::Push+59
clr!FillInRegTypeMap+198
clr!FillInRegTypeMap+c1
[[DebuggerU2MCatchHandlerFrame]]
clr!FinalizerThread::FinalizerThreadStart+10a
clr!Thread::intermediateThreadProc+86
kernel32!BaseThreadInitThunk+14
ntdll!RtlUserThreadStart+21
Any idea what might be going on?
c# asp.net-mvc memory-leaks
asked Jan 2 at 19:15
TheDizzleTheDizzle
56921131
1
Are multiple users accessing the same objects held in memory...? You may need some locks
– O.H.
Jan 2 at 19:19
Do many of your types have finalizers? If so what are you doing in the finalizers? The stack above just shows that the thread is waiting. It isn't necessarily blocked.
– Brian Rasmussen
Jan 2 at 19:19
Your finalizer thread looks fine, but that's a lot of finalizable objects, especially for a web application. Are you disposing everything properly? To investigate a hang, debugdiag isn't the best tool. Try attaching the Visual studio debugger and look at the "parallel stacks" window
– Kevin Gosse
Jan 2 at 19:21
There are areas in the application whereGC.Collect()is being used as well as Close/Dispose.
– TheDizzle
Jan 2 at 19:42
Why are you calling GC.Collect() directly? That's almost always a bad idea
– Fran
Jan 2 at 20:11
|
show 2 more comments
0
0
0
Whenever someone tries to access my application, if more than one person is using it it starts to hang. I recreated the issue and ran DebugDiag memory check and get this warning.
Number of objects ready for finalization: 457779
It then tells me that the finalizer thread may be blocked.
As the number of finalizable objects is more than 0, please check the finalizer thread to see if it is blocked or active
Finalizer Thread
ntdll!NtWaitForSingleObject+14
KERNELBASE!WaitForSingleObjectEx+8f
clr!CLREventBase::WaitEx+17c
clr!CLREventBase::WaitEx+113
clr!CLREventBase::WaitEx+7c
clr!FinalizerThread::WaitForFinalizerEvent+44
clr!FinalizerThread::FinalizerThreadWorker+54
clr!Frame::Push+59
clr!FillInRegTypeMap+198
clr!FillInRegTypeMap+c1
[[DebuggerU2MCatchHandlerFrame]]
clr!FinalizerThread::FinalizerThreadStart+10a
clr!Thread::intermediateThreadProc+86
kernel32!BaseThreadInitThunk+14
ntdll!RtlUserThreadStart+21
Any idea what might be going on?
c# asp.net-mvc memory-leaks
asked Jan 2 at 19:15
TheDizzleTheDizzle
56921131
Whenever someone tries to access my application, if more than one person is using it it starts to hang. I recreated the issue and ran DebugDiag memory check and get this warning.
Number of objects ready for finalization: 457779
It then tells me that the finalizer thread may be blocked.
As the number of finalizable objects is more than 0, please check the finalizer thread to see if it is blocked or active
Finalizer Thread
ntdll!NtWaitForSingleObject+14
KERNELBASE!WaitForSingleObjectEx+8f
clr!CLREventBase::WaitEx+17c
clr!CLREventBase::WaitEx+113
clr!CLREventBase::WaitEx+7c
clr!FinalizerThread::WaitForFinalizerEvent+44
clr!FinalizerThread::FinalizerThreadWorker+54
clr!Frame::Push+59
clr!FillInRegTypeMap+198
clr!FillInRegTypeMap+c1
[[DebuggerU2MCatchHandlerFrame]]
clr!FinalizerThread::FinalizerThreadStart+10a
clr!Thread::intermediateThreadProc+86
kernel32!BaseThreadInitThunk+14
ntdll!RtlUserThreadStart+21
Any idea what might be going on?
c# asp.net-mvc memory-leaks
c# asp.net-mvc memory-leaks
asked Jan 2 at 19:15
TheDizzleTheDizzle
56921131
asked Jan 2 at 19:15
TheDizzleTheDizzle
56921131
edited Jan 2 at 21:15
TheDizzle
asked Jan 2 at 19:15
TheDizzleTheDizzle
56921131
asked Jan 2 at 19:15
TheDizzleTheDizzle
56921131
asked Jan 2 at 19:15
TheDizzleTheDizzle
56921131
56921131
1
Are multiple users accessing the same objects held in memory...? You may need some locks
– O.H.
Jan 2 at 19:19
Do many of your types have finalizers? If so what are you doing in the finalizers? The stack above just shows that the thread is waiting. It isn't necessarily blocked.
– Brian Rasmussen
Jan 2 at 19:19
Your finalizer thread looks fine, but that's a lot of finalizable objects, especially for a web application. Are you disposing everything properly? To investigate a hang, debugdiag isn't the best tool. Try attaching the Visual studio debugger and look at the "parallel stacks" window
– Kevin Gosse
Jan 2 at 19:21
There are areas in the application whereGC.Collect()is being used as well as Close/Dispose.
– TheDizzle
Jan 2 at 19:42
Why are you calling GC.Collect() directly? That's almost always a bad idea
– Fran
Jan 2 at 20:11
|
show 2 more comments
1
Are multiple users accessing the same objects held in memory...? You may need some locks
– O.H.
Jan 2 at 19:19
Do many of your types have finalizers? If so what are you doing in the finalizers? The stack above just shows that the thread is waiting. It isn't necessarily blocked.
– Brian Rasmussen
Jan 2 at 19:19
Your finalizer thread looks fine, but that's a lot of finalizable objects, especially for a web application. Are you disposing everything properly? To investigate a hang, debugdiag isn't the best tool. Try attaching the Visual studio debugger and look at the "parallel stacks" window
– Kevin Gosse
Jan 2 at 19:21
There are areas in the application whereGC.Collect()is being used as well as Close/Dispose.
– TheDizzle
Jan 2 at 19:42
Why are you calling GC.Collect() directly? That's almost always a bad idea
– Fran
Jan 2 at 20:11
1
1
Are multiple users accessing the same objects held in memory...? You may need some locks
– O.H.
Jan 2 at 19:19
Are multiple users accessing the same objects held in memory...? You may need some locks
– O.H.
Jan 2 at 19:19
Do many of your types have finalizers? If so what are you doing in the finalizers? The stack above just shows that the thread is waiting. It isn't necessarily blocked.
– Brian Rasmussen
Jan 2 at 19:19
Do many of your types have finalizers? If so what are you doing in the finalizers? The stack above just shows that the thread is waiting. It isn't necessarily blocked.
– Brian Rasmussen
Jan 2 at 19:19
Your finalizer thread looks fine, but that's a lot of finalizable objects, especially for a web application. Are you disposing everything properly? To investigate a hang, debugdiag isn't the best tool. Try attaching the Visual studio debugger and look at the "parallel stacks" window
– Kevin Gosse
Jan 2 at 19:21
Your finalizer thread looks fine, but that's a lot of finalizable objects, especially for a web application. Are you disposing everything properly? To investigate a hang, debugdiag isn't the best tool. Try attaching the Visual studio debugger and look at the "parallel stacks" window
– Kevin Gosse
Jan 2 at 19:21
There are areas in the application where
GC.Collect() is being used as well as Close/Dispose.– TheDizzle
Jan 2 at 19:42
There are areas in the application where
GC.Collect() is being used as well as Close/Dispose.– TheDizzle
Jan 2 at 19:42
Why are you calling GC.Collect() directly? That's almost always a bad idea
– Fran
Jan 2 at 20:11
Why are you calling GC.Collect() directly? That's almost always a bad idea
– Fran
Jan 2 at 20:11
|
show 2 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54011947%2fobjects-ready-for-finalization-are-being-blocked%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54011947%2fobjects-ready-for-finalization-are-being-blocked%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Are multiple users accessing the same objects held in memory...? You may need some locks
– O.H.
Jan 2 at 19:19
Do many of your types have finalizers? If so what are you doing in the finalizers? The stack above just shows that the thread is waiting. It isn't necessarily blocked.
– Brian Rasmussen
Jan 2 at 19:19
Your finalizer thread looks fine, but that's a lot of finalizable objects, especially for a web application. Are you disposing everything properly? To investigate a hang, debugdiag isn't the best tool. Try attaching the Visual studio debugger and look at the "parallel stacks" window
– Kevin Gosse
Jan 2 at 19:21
There are areas in the application where
GC.Collect()is being used as well as Close/Dispose.– TheDizzle
Jan 2 at 19:42
Why are you calling GC.Collect() directly? That's almost always a bad idea
– Fran
Jan 2 at 20:11