dotMemory shows ReaderWriterLocks growing

Hi. I have a multi-threaded service application, and I have a growing number of these ReaderWriterLocks when I run dotMemory snapshots. See pic. Does this mean it is stuck in finalizer? How can I trace it to what the cause is? I've been using dotMemory and have tracked down quite a few things (great tool), but this one doesn't trace to any of my code or anything that is being called directly? Help.

1 comment
Comment actions Permalink



You've got a big Finalization Queue, that means that GC could be overloaded, please refer to the corresponding help article -
Generally, the number of such objects should be reduced as it could affect performance.
Thank you.

Please sign in to leave a comment.