Skip to content

8357034: GifImageDecoder can produce wrong transparent pixels #25264

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 27 commits into
base: master
Choose a base branch
from

Conversation

mickleness
Copy link
Contributor

@mickleness mickleness commented May 16, 2025

If there are two consecutive frames that use DISPOSAL_SAVE, but the transparent pixel index changed: we might accidentally send the wrong data to the ImageConsumer.

We already had logic that submits info "the hard way" (see comment in code); this PR just makes sure we trigger that block.

I wrote four PRs that share the GifComparison class in this PR. Once any of them clear code review the other PRs will be much simpler:

  1. 8357034 (this one)
  2. 8356137
  3. 8356320
  4. 8351913

Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8357034: GifImageDecoder can produce wrong transparent pixels (Bug - P4)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25264/head:pull/25264
$ git checkout pull/25264

Update a local copy of the PR:
$ git checkout pull/25264
$ git pull https://git.openjdk.org/jdk.git pull/25264/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25264

View PR using the GUI difftool:
$ git pr show -t 25264

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25264.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented May 16, 2025

👋 Welcome back mickleness! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented May 16, 2025

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk openjdk bot added the rfr Pull request is ready for review label May 16, 2025
@openjdk
Copy link

openjdk bot commented May 16, 2025

@mickleness The following label will be automatically applied to this pull request:

  • client

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@mlbridge
Copy link

mlbridge bot commented May 16, 2025

Webrevs

@mickleness mickleness marked this pull request as draft May 16, 2025 10:39
@openjdk openjdk bot removed the rfr Pull request is ready for review label May 16, 2025
@openjdk
Copy link

openjdk bot commented May 26, 2025

⚠️ @mickleness This pull request contains merges that bring in commits not present in the target repository. Since this is not a "merge style" pull request, these changes will be squashed when this pull request in integrated. If this is your intention, then please ignore this message. If you want to preserve the commit structure, you must change the title of this pull request to Merge <project>:<branch> where <project> is the name of another project in the OpenJDK organization (for example Merge jdk:master).

This makes the main() method much less useful, so I removed it too. (I originally used this class to explore a folder of hundreds of gifs to look for discrepancies. But the discrepancies were rarely only on the last frame.)

This is in response to:
openjdk#25044 (comment)
This can be used by multiple gif tests in this directory.

This is in response to:
openjdk#25044 (review)
@bridgekeeper
Copy link

bridgekeeper bot commented Jun 13, 2025

@mickleness This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply issue a /touch or /keepalive command to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client [email protected] rfr Pull request is ready for review
Development

Successfully merging this pull request may close these issues.

1 participant