Replies: 2 comments
-
Can you please take a look at this please, @Maoni0 ? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have a service exhibiting a memory leak in a weird way: seems like GC refuses to do gen2 collections and reasons to that are unknown.
So gen2 keeps growing, but I don't see GC even trying to clean up gen2. We've taken few ~30sec PerfView traces and not one of them reported a gen2 collection.
An example of PerfView report:
I think the reason for the leak is a constant GCHandle grow. So far with heap of 10 gigbytes (8.2 of which is gen2) there are 7.3 million GCHandles reported. Looking for
clr!GCHandleStore::CreateHandleOfType
wasn't fruitful because callers are knowns framework functions.I need some help on how to diagnose this kind of issue. The weirdest thing to me, again, is that gc refuses to make gen2 collections. Every gen0/gen1 collection ends up cleaning 300 to 500 megabytes of data and it seems fine with just that. I'm confused whether this is a leak after all or just gc refusing to clean up these handles. Note that there are other services with the same verision/dlls and they do not behave like that.
Beta Was this translation helpful? Give feedback.
All reactions