[ 
https://issues.apache.org/jira/browse/IGNITE-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784349#comment-16784349
 ] 

Ignite TC Bot commented on IGNITE-11152:
----------------------------------------

{panel:title=--> Run :: All: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3231783&buildTypeId=IgniteTests24Java8_RunAll]

> IgniteTxManager.idMap possible memory leak
> ------------------------------------------
>
>                 Key: IGNITE-11152
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11152
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Stepachev Maksim
>            Assignee: Roman Kondakov
>            Priority: Major
>              Labels: memory-leak, mvcc_stabilization_stage_1, transactions
>             Fix For: 2.8
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> CacheContinuousQueryAsyncFailoverMvccTxSelfTest.testMultiThreadedFailover 
> sometimes finished with OMM.
> Heapdump analyze showed that leak happened in IgniteTxManager.idMap, this map 
> contains *2_097_152* instances of GridNearTxLocal with *ACTIVE state* and 
> *without* finishFut *and prepFut.*
>  
> {code:java}
> while (!updated) {
>  try {
>  prevVal = (Integer)qryClnCache.getAndPut(key, val);
> updated = true;
>  }
>  catch (CacheException e) {
>  assertSame(atomicityMode(), CacheAtomicityMode.TRANSACTIONAL_SNAPSHOT);
>  }
>  }
> {code}
>  
>  
> Possible the CacheException is common and may hide wrong cases. Change it at 
> specific (ignite-10976).  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to