# JUCE 8 - Memory Leak

**URL:** <https://forum.juce.com/t/juce-8-memory-leak/61811>\
**Category:** General JUCE discussion\
**Created:** [June 12, 2024, 2:43pm UTC](https://forum.juce.com/t/juce-8-memory-leak/61811 "2024-06-12T14:43:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![reuk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/reuk/32/21494_2.png) [@reuk](https://forum.juce.com/u/reuk)\
**Post date:** [June 24, 2024, 11:17am UTC](https://forum.juce.com/t/juce-8-memory-leak/61811/4 "2024-06-24T11:17:08Z")

</div>

Thanks for reporting, there’s a fix for this issue on the develop branch:

> <https://github.com/juce-framework/JUCE/commit/203934d949306e8c0b94f27a327012b5881238a5>
>
> Before this change, after running a JUCE app on Windows under a
> debugger, and qu…itting it normally (e.g. pressing the close title
> button), the output log would display some memory leak diagnostics. This
> is because HarfBuzz expects to clean up statics using atexit, but atexit
> was not enabled. This change enables atexit on supported platforms,
> including Windows.

See also:

> [@Detected memory leaks after update to v8](https://forum.juce.com/t/detected-memory-leaks-after-update-to-v8/61892):
>
> JUCE v8.0.0 Detected memory leaks! Dumping objects -\> {3138} normal block at 0x0000022AE186FAD0, 6 bytes long. Data: \<es-es \> 65 73 2D 65 73 00 {3137} normal block at 0x0000022AE186FFD0, 16 bytes long. Data: \<@ r \* \* \> 40 B0 72 E1 2A 02 00 00 D0 FA 86 E1 2A 02 00 00 {2935} normal block at 0x0000022AE16BC610, 2 bytes long. Data: \<c \> 63 00 {2934} normal block at 0x0000022AE172B040, 16 bytes long. Data: \< k \* \> 00 00 00 00 00 00…

---

_[View the full topic](https://forum.juce.com/t/juce-8-memory-leak/61811)._