Summary: The more statements (load) are executed, the bigger the memory leak they cause leading to OOM. These are leaked in the JDBC connector.

Problem: JDBC connector executes sql statements and uses a set to keep track of them. On connection close, those objects should be cleared, but they are not, causing a memory leak that leads to OOM.

Implication: OOM in client side due to leaked statements.