Nicolas Roduit

As the goal is to find a solution that meets all usage contexts, here are the benefits of using the Cleaner method: - allows to replace properly `finalize()` - brings...

@davidreis97 you can test this [PR](https://github.com/opencv/opencv/pull/23467). We've been using it for a while in production without any problems. If you're really using memory intensively, you can always release it manually...

@sgjava Look carefully, all these classes register a Cleaner.

PhantomReference is not meant to replace AutoCloseable and try-with-resources, it’s designed to handle non-deterministic cleanup tasks when the exact timing of resource release is less critical or not feasible through...

@sgjava I understand that you have a different point of view. I have already replied to it with https://github.com/opencv/opencv/issues/22260#issuecomment-1310143046. If you believe your approach is more effective, I encourage you...

@vlsi The messages you pointed is more related to driver-specific behaviors, whereas the current issue is about using finalize() in OpenCV's Java bindings to free native (JNI) memory held by...

As you do not use the bug template, please provide minimal information like the version

Thank you for your report. If the original series is coronal or sagittal, the geometric correction is currently not applied because some changes are necessary in the processing pipeline. These...

I would say this is a feature rather than a bug, because when a Presentation State (GSPS) is applied, the window/level (default values, LUT and LUT shape) can be overridden...

A DICOM Presentation State (GSPS / PR) can contain more than just graphics: it may specify Window&Level, modality/VOI LUTs, image position/size, calibration, display area, zoom/rotation, and more. Weasis applies the...