-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8362898: Remove finalize() methods from javax.imageio TIFF classes #26416
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
Conversation
👋 Welcome back prr! A progress list of the required criteria for merging this PR into |
@prrace This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 181 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
/integrate |
@prrace This pull request has not yet been marked as ready for integration. |
/integrate |
@prrace This pull request has not yet been marked as ready for integration. |
/integrate |
Going to push as commit dc4d9b4.
Your commit was automatically rebased without conflicts. |
Remove finalize from TIFF ImageIO implementatation classes.
Following copied from the bug description
The TIFF image (de)compressors can make use of a JPEG reader / writer
Like all ImageIO readers and writers, once done, the owner should call their dispose() method.
This is currently done with finalize() to ensure it isn't missed.
This can be migrated to a Disposer.
However, the most common case is that it is the ImageIO built-in JPEGImageReader and JPEGImageWriter
that is located and that already implements a Disposer. So there is no need to add a Disposer for that.
We only need to add it if we find some other reader/writer.
With enough work, it might be possible for the TIFF compressor/decompressor classes to work out when
they are really done and avoid a Disposer at all. But it could also be that they instead need to discard
them when a specific task is done and then obtain a new one.
That would be much more overhead than just adding a Disposer for the rare case and regardless
of what is done in the TIFF code, the built in JPEG classes will install their own Disposer so I don't
think I want to pursue that route.
I also noticed that TIFFBaseJPEGCompressor.java can replace the current writer if it doesn't satisfy a need.
In that case it just nulls it out and doesn't call dispose() and of course finalize() will then refer to the replacement.
So I added direct calls to dispose() in such a case. That was definitely necessary with the finalize() code
but the Disposer would have taken care of it anyway, so it isn't strictly needed with the new code but
it is still good to do it early if you can.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/26416/head:pull/26416
$ git checkout pull/26416
Update a local copy of the PR:
$ git checkout pull/26416
$ git pull https://git.openjdk.org/jdk.git pull/26416/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 26416
View PR using the GUI difftool:
$ git pr show -t 26416
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/26416.diff
Using Webrev
Link to Webrev Comment