Description:
The NdbEvent-API has an internal list relating GCIs to event operations
which has event data for each GCI. (The gci_op / gci_ops list)
This structure is part of the EventBufData_list structure, which also
manage a list of EventBufData to be delivered.
There are several placed where we empties the EventBufData_list by
freeing all EventBufData from it. *iff* the EventBufData_list
is non-empty ::free_list() will be called to recycle the EventBufData
objects *and* their gci_op(s). (No leaks)
However, there can be remaining gci_op(s) in the EventBufData_list,
referring the last consumed EventBufData item, even if the list
of EventBufData items is empty. As ::free_list is not called for
empty list, these gci_op(s) leaked if not explicitly handled.
The code for handling these dangling gci_op(s) is missing from
- NdbEventBuffer::~NdbEventBuffer()
- NdbEventBuffer::remove_op()
- NdbEventBuffer::move_data()
Where it *is* handled, the implementation is just cluttered by first
freeing the EventDataList, then freeing gci_op(s) which was not handled
by free_list() (Which actually *is* part of the list)
How to repeat:
Run Valgrind with some of the ATR test_event testcases.
.. or inspect code..
