|
for (size_t id = 1; id < prm.batchData_.size(); ++id) { |
The for loop in the indexing thread makes incorrect assumption that first element in batch will always be handled by the primer functions. First element is only added if ELList is empty, thus all subsequent AddBatch calls skip the first element. Issue only happens when using multiple threads.
Did local changes to fix:
- Add
size_t batch_start_index prop to Thread params.
- Init
batch_start_index with start_add on primer function
- Change for loop in thread to init with
batch_start_index rather than 1