[
https://issues.apache.org/jira/browse/KAFKA-16089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804630#comment-17804630
]
Lucas Brutschy commented on KAFKA-16089:
----------------------------------------
[https://github.com/apache/kafka/pull/14852] was identified as a very likely
suspect for introducing this leak - A soak test without the change ran with
very little native memory growth. The change will be reverted in 3.7, until a
solution was found
> Kafka Streams still leaking memory
> ----------------------------------
>
> Key: KAFKA-16089
> URL: https://issues.apache.org/jira/browse/KAFKA-16089
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 3.7.0
> Reporter: Lucas Brutschy
> Priority: Blocker
> Fix For: 3.7.0
>
> Attachments: graphviz (1).svg
>
>
> In
> [https://github.com/apache/kafka/commit/58d6d2e5922df60cdc5c5c1bcd1c2d82dd2b71e2]
> a leak was fixed in the release candidate for 3.7.
>
> However, Kafka Streams still seems to be leaking memory (just slower) after
> the fix.
>
> Attached is the `jeprof` output right before a crash after ~11 hours.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
