Open
Bug 1278776
Opened 8 years ago
Updated 1 year ago
Add a way to assert that we don't expand StreamingLexer's buffer unexpectedly
Categories
(Core :: Graphics: ImageLib, defect, P3)
Core
Graphics: ImageLib
Tracking
()
NEW
People
(Reporter: seth, Unassigned)
References
Details
(Whiteboard: [gfx-noted])
In general we should be setting StreamingLexer's size template parameter in such a way as to ensure that fixed-size states don't require expanding the buffer. It's also usually best practice to read variable-size state data in unbuffered mode. It'd be ideal to ensure that we're doing this by asserting that we never expand the buffer in StreamingLexer. If we do it there, we can identify the state that caused the problem. What complicates this is that if we make this a hard policy, we can't use StreamingLexer to read in images row by row, which is incredibly convenient for some image formats. It's worth thinking about how to preserve this capability while still letting us detect when we *unexpectedly* expand the buffer.
Updated•8 years ago
|
Whiteboard: [gfx-noted]
Comment 1•8 years ago
|
||
> It's worth thinking about how to preserve this
> capability while still letting us detect when we *unexpectedly* expand the
> buffer.
Some kind of flag you can set to make the checking more lenient?
Updated•7 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•