# How reliable is Visual Studio leak detection?

**URL:** <https://forum.juce.com/t/how-reliable-is-visual-studio-leak-detection/30299>\
**Category:** Windows\
**Created:** [November 11, 2018, 9:55pm UTC](https://forum.juce.com/t/how-reliable-is-visual-studio-leak-detection/30299 "2018-11-11T21:55:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![daniel](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/daniel/32/790_2.png) [@daniel](https://forum.juce.com/u/daniel)\
**Post date:** [November 11, 2018, 9:59pm UTC](https://forum.juce.com/t/how-reliable-is-visual-studio-leak-detection/30299/2 "2018-11-11T21:59:07Z")

</div>

This seems to be an unavoidable leak, see Jules’ answer here:

> [@Memory leaks with VST plug-ins and Windows XP](https://forum.juce.com/t/memory-leaks-with-vst-plug-ins-and-windows-xp/9277/4):
>
> Yeah, you’re only leaking two 8-byte objects, which are almost certainly just win32 message blocks. Don’t worry about it - you’d need to load/unload your plugin millions of times before the amount of leaked memory became a problem!

---

_[View the full topic](https://forum.juce.com/t/how-reliable-is-visual-studio-leak-detection/30299)._