Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@rzumer
Copy link
Collaborator

@rzumer rzumer commented Oct 25, 2019

Found this while fuzzing and took the easy way out. An alternative or complementary solution would be to assert that the frame size is valid and display a proper error message if it is not (I could not find the minimum frame size requirements in the spec, but I seem to recall they exist).

@lu-zero
Copy link
Collaborator

lu-zero commented Oct 25, 2019

Another option would be to disable lrf for images smaller than something. I doubt it would have a beneficial impact if any.

@coveralls
Copy link
Collaborator

coveralls commented Oct 25, 2019

Coverage Status

Coverage increased (+0.004%) to 75.52% when pulling 6f54917 on rzumer:lrf-crash into 1618f98 on xiph:master.

This fixes a crash in LRF at widths or heights of 1 px
as a side effect of disabling restoration at sizes where
it is not likely to improve quality.
@rzumer
Copy link
Collaborator Author

rzumer commented Oct 25, 2019

@lu-zero I updated the PR with this solution and added an assertion when initializing the restoration context.

@rzumer rzumer merged commit 35b27b4 into xiph:master Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants