Comments
Sort by recent activity
Thanks StephenC for the reply.
I already checked out those YT vids before so I could get an idea about how to use the product. I suppose I was just double checking that we were going through the process right.
The biggest take away item from the vids was from vid #2 .. about how it said we need to cut a reference to an object so the hierarchy can get GC'd.
Looking at the Renention graph, i was getting so confused because all the data kept pointing back to NLog. The strings were NLog related (connection strings, etc). The Net Socket stuff was also NLog related. It's like it was not releasing some network level code. Our assumption: NLog is ok, but my code is not. After all, NLog is a popular application that is being used by many, many people which suggests it's pretty stable, etc.
I kept thinking .. how can i make it so that those NLog delegates (which Memory Profiler 6 was showing me) could get disconnected/cut?
Until I thought for a second: is anyone else having a memory leak issue with NLog...
google points me to: http://github.com/jkowalski/NLog/commit ... d363ee4b95
Downloaded the latest nightly build and viola! memory leak gone.
Awesome work RedGate [image] I would never have thought the error lied with the old(er) NLog dll I was using.
Cheers [image]
-PK- / comments
Thanks StephenC for the reply.
I already checked out those YT vids before so I could get an idea about how to use the product. I suppose I was just double checking that we were going through the pr...