-
Notifications
You must be signed in to change notification settings - Fork 47
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fixed valgrind error where MQ coder was accessing uninitialized memor…
…y in RESTART mode. Unfortunately, there is still a problem with RESTART: lossless encoding with RESTART produces a lossy image.
- Loading branch information
Aaron Boxer
committed
Mar 18, 2016
1 parent
b52e9db
commit 3d9ee7a
Showing
2 changed files
with
17 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3d9ee7a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the important line. For bpno == 0, there is no termination. That is why you are seeing the encoder go into an endless loop. Simply remove
bpno > 0
and it should fix the valgrind error. Of course, lossless encoding may still be lossy, but that is a bigger issue.