jgaalen commented on issue #6237: URL: https://github.com/apache/jmeter/issues/6237#issuecomment-2022147390
I made a heapdump and looked at it. It seems that the responseData is filled up for the transactionSampleResult.subResults. Somehow the transactionSampler needs to be cleared right after the data is sent to the listeners, but it isn't and kept in memory until the end of the thread. With large responseData/subresults this can pile up. I've started researching as I've had tests with just 300-500 concurrent Vusers but many requests in transactions with memory exceeding 16GB and ending in OOM everytime. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org