Unbounded memory usage in LBDB
Ronak mentioned finding a vector in LBDB that stores location records, which we simply do 'push_back()' on always, even though some entries are invalidated in the middle of the vector over time.
Instead of using push_back we can scan the vector for a NULL entry, and maybe keep track of the first NULL element in the vector so we have a guess at where to start the scan from always.
#2 Updated by Ronak Buch 12 months ago
- Status changed from New to Implemented