Loading...

XML

Word

Printable

Fix Build:
CR2
Steps to Reproduce:
Hide

Unzip attached 01772218_ksession_leak_timer_loop02.zip

mvn test

It will print "hello" repeatedly

After you confirm several "hello", capture a heap dump

Look into the heap dump with an analyzer tool (e.g. MemoryAnalyzer) and see several ksession are retained in the heap

It will finally lead to OOME
Show
Unzip attached 01772218_ksession_leak_timer_loop02.zip mvn test It will print "hello" repeatedly After you confirm several "hello", capture a heap dump Look into the heap dump with an analyzer tool (e.g. MemoryAnalyzer) and see several ksession are retained in the heap It will finally lead to OOME

If you have a process with Timer in a loop and run it with PerProcessInstance, ksession instances are held in heap so it results in memory leak.

clones

RHPAM-64 ksession leak with Timer+Loop+PerProcessInstance