SST: Memory leaks on reader disconnection
Created by: keichi
While doing scalability tests with JAXA's workflow, I found that reconnecting the reader causes memory leaks. If I disconnect and connect the reader repeatedly, the memory footprint of the writers (except writer 0) keeps increasing. It seems that the queued timesteps are not being released when the reader disconnects.
The engine parameters are: RendezvousReaderCount=0
, QueueLimit=2
, QueueFullPolicy=Discard
. I'm seeing the same issue with gray-scott and pdf_calc as well, so I don't think it's an issue with JAXA's app or system.