DBohner-(db)
Legendary Poster
Howdy,
Frosty had a thread a couple years ago - "Finding Memory Leaks" that got no responses.... Hopefully, "Round II" will get some advice?
Situation:
- Heavily Customized System
- Recent Go Live, Billions of Users are Starting to Log in
- We are seeing some "out of heap", and other memory issues, occasionally, in crash logs (Kernel & Zombie, predominately)
Crash logs really don't share a lot of information - basically they tell us what might have been in use at the time something became viral and went all zombie on us.
So the question - during development, is there a formal process to identify what might be leaking?
There's an MSDN article - could this work during local development, then just remove the leak specific syntax during the development cycle:
https://msdn.microsoft.com/en-us/library/x98tx3cf.aspx
What do you gurus do, out there, that helps identify you leaks?
Thanks in Advance!
(db)
Frosty had a thread a couple years ago - "Finding Memory Leaks" that got no responses.... Hopefully, "Round II" will get some advice?
Situation:
- Heavily Customized System
- Recent Go Live, Billions of Users are Starting to Log in
- We are seeing some "out of heap", and other memory issues, occasionally, in crash logs (Kernel & Zombie, predominately)
Crash logs really don't share a lot of information - basically they tell us what might have been in use at the time something became viral and went all zombie on us.
So the question - during development, is there a formal process to identify what might be leaking?
There's an MSDN article - could this work during local development, then just remove the leak specific syntax during the development cycle:
https://msdn.microsoft.com/en-us/library/x98tx3cf.aspx
What do you gurus do, out there, that helps identify you leaks?
Thanks in Advance!
(db)