Project

General

Profile

Bug #1961

Unbounded memory usage in LBDB

Added by Sam White 12 months ago. Updated 12 months ago.

Status:
Merged
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
08/08/2018
Due date:
% Done:

0%


Description

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.

History

#1 Updated by Sam White 12 months ago

I think it would be good to have this fixed for 6.9.0 since it should be simple and non-API-breaking

#2 Updated by Ronak Buch 12 months ago

  • Status changed from New to Implemented

#3 Updated by Evan Ramos 12 months ago

  • Status changed from Implemented to Merged

#4 Updated by Evan Ramos 12 months ago

  • Target version set to 6.9.0

Also available in: Atom PDF