# How we tracked down a Go 1.24 memory regression across hundreds of pods | Datadog

**URL:** <https://forum.devtalk.com/t/how-we-tracked-down-a-go-1-24-memory-regression-across-hundreds-of-pods-datadog/207683>\
**Category:** Backend In The News\
**Tags:** via-news-bot, go, in-the-news\
**Created:** [21 July 2025 17:06 UTC](https://forum.devtalk.com/t/how-we-tracked-down-a-go-1-24-memory-regression-across-hundreds-of-pods-datadog/207683 "2025-07-21T17:06:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CommunityNews](https://forum.devtalk.com/user_avatar/forum.devtalk.com/communitynews/32/1113_2.png) [@CommunityNews](https://forum.devtalk.com/u/CommunityNews)\
**Post date:** [21 July 2025 17:06 UTC](https://forum.devtalk.com/t/how-we-tracked-down-a-go-1-24-memory-regression-across-hundreds-of-pods-datadog/207683/1 "2025-07-21T17:06:30Z")

</div>

> We rolled out Go 1.24 and saw a memory regression. Here’s how we dug into system metrics, uncovered a bug in the runtime allocator, and worked with the Go team to help fix it.

Read in full here:

> **[How we tracked down a Go 1.24 memory regression across hundreds of pods |...](https://www.datadoghq.com/blog/engineering/go-memory-regression/)**
>
> We rolled out Go 1.24 and saw a memory regression. Here's how we dug into system metrics, uncovered a bug in the runtime allocator, and worked with the Go team to help fix it.