[
https://issues.apache.org/jira/browse/IGNITE-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117908#comment-17117908
]
Maxim Muzafarov commented on IGNITE-10959:
------------------------------------------
[~Pavlukhin]
Hello, I've found some code changes probably related to the current issue in
GGCE (suppose associated with GG-17432). At first glance, they related to
memory consumption.
I'm not diving deep into those details yet, but can you please share some
details at those fix? I'm going to continue the investigation, should I?
Are there any corner cases left uncovered? I've applied those changes and
checked the attached reproducer {{CacheContinuousQueryMemoryUsageTest}}
locally, it seems it still fails (the \{{backupQ}} remains uncleared).
> Memory leaks in continuous query handlers
> -----------------------------------------
>
> Key: IGNITE-10959
> URL: https://issues.apache.org/jira/browse/IGNITE-10959
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Denis Mekhanikov
> Assignee: Maxim Muzafarov
> Priority: Critical
> Attachments: CacheContinuousQueryMemoryUsageTest.java,
> CacheContinuousQueryMemoryUsageTest.result,
> CacheContinuousQueryMemoryUsageTest2.java,
> Memory_blowup_in_Ignite_CacheContinuousQueryHandler.txt,
> Memory_blowup_in_Ignite_CacheContinuousQueryHandler.txt,
> Memory_blowup_in_Ignite_CacheContinuousQueryHandler.txt,
> continuousquery_leak_profile.png
>
>
> Continuous query handlers don't clear internal data structures after cache
> events are processed.
> A test, that reproduces the problem, is attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
