Project

General

Profile

Actions

Bug #4955

closed

stream: too aggressive pruning in lossy streams

Added by Jeff Lucovsky 9 months ago. Updated 8 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

Pruning of StreamBufferBlocks could remove blocks that fell entirely after the target offset due to a logic error. This could lead to data being evicted that was still meant to be processed in the app-layer parsers.


Related issues 1 (0 open1 closed)

Copied from Bug #4953: stream: too aggressive pruning in lossy streamsClosedVictor JulienActions
Actions #1

Updated by Jeff Lucovsky 9 months ago

  • Copied from Bug #4953: stream: too aggressive pruning in lossy streams added
Actions #2

Updated by Jeff Lucovsky 9 months ago

  • Status changed from Assigned to In Progress

Cherry-pick commit(s)
- 258415b23f455e3aaee6d97a0e485e5690959011 (partial)
- 544ff0fb52cad0ee35dfd968bd775703737c4ef6
- 78f5e082f5188204606ab9ceb5044447e49aaca2

Actions #3

Updated by Jeff Lucovsky 9 months ago

  • Status changed from In Progress to In Review
Actions #4

Updated by Jeff Lucovsky 8 months ago

Cherry-pick commit 544ff0fb removed per request.

Actions #5

Updated by Jeff Lucovsky 8 months ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF