You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the first pass of a code block, if there were no bytes output by the mq coder,
then the OpenJPEG mq coder will store a rate of -1 for this first pass.
After a correction factor is added, this is stored as a positive rate of 2. But still, this looks
like a bug to me: passes with zero rates are given different rates, depending on when they
occur in the code stream.
Also, these lines could cause an access to uninitialized memory:
This part of the code has been recently significantly reworked. I believe the above is fixed with that, but difficult to say given there's no reproducer given in the ticket. So closing. Re-open if you believe the issue is still there
On the first pass of a code block, if there were no bytes output by the mq coder,
then the OpenJPEG mq coder will store a rate of -1 for this first pass.
After a correction factor is added, this is stored as a positive rate of 2. But still, this looks
like a bug to me: passes with zero rates are given different rates, depending on when they
occur in the code stream.
Also, these lines could cause an access to uninitialized memory:
Because the rate is 2, but in fact no data has been output.
Looks like this is currently being reported by valgrind
The text was updated successfully, but these errors were encountered: