~Cs assertion failure after setLimit()
Cs' destructor triggers the following assertion if setLimit is used:
Assertion failed: (m_freeCsEntries.size() == m_nMaxPackets), function ~Cs, file ../daemon/table/cs.cpp, line 56.
It doesn't seem to matter if the limit is increased or decreased. Please see attached test cases.
#2 Updated by Alex Afanasyev over 5 years ago
- Category set to Tables
- Assignee set to Ilya Moiseenko
- Target version set to v0.2
CS constructor pre-allocates the specified number of entries and setLimit doesn't do anything, except updating number of max packets and evicting items (and eventually causing segfault).
What we need here is to update setLimit to do this pre-allocation (re-allocation).