Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
1.0.2, 1.1.0-beta
-
None
Description
see https://github.com/mariadb-corporation/mariadb-connector-r2dbc/issues/23
There is 2 possibles cases where this can occurs :
- when throwing an exception like a wrong conversion (i.e a number to big to fit in a Integer value for example)
- when issuing a command with resultset and not consuming the result either with getRowsUpdated() or mapping resultset.
In those cases, result buffer are not released to pool before buffer are garbage collected.