Hi Evan
I seem to still be having problems closing datasets in Java resulting in a JVM
crash, using gdal-3-13-3_x64 downloaded from the GISInternals site. Below is
the stack trace information.
--- T H R E A D ---
Current thread (0x01ffd39932c0): JavaThread "Fin
it will eventually become incorrect.
Thanks,
Tom
On Fri, Jul 11, 2025, at 11:24 AM, Even Rouault wrote:
> Tom,
>
> you can drop the clcache dependency if that helps. Otherwise try to
> create a conda env from scratch (if you didn't do that)
>
> Even
>
> Le 11/0
Newbie here. As the title says I am trying to set up a build environment.
I was trying to follow the instructions from the website:
https://gdal.org/en/stable/development/dev_environment.html
I got to the step to install the compiler and got an error about conflicts and
the process stopped. D
Hi Even
I just wanted to update you and provide a record for posterity with the results
of me playing around with gdal/java and resource management.
It appears to me that Dataset objects should not be closed from Java client
code. If you do then often there will be an access violation (native
Thank Evan!
I am planning on being read-only for now.
My program is interactive and potentially long-lived, and the user interface
can be used to open layers at different times. If I miss closing a Dataset will
the garbage collector eventually take care of this? Or is it important to
always
Hi
I am new to using gdal/ogr in Java via the swig bindings and I am trying to
figure things out by googling around. I have looked at the API documentation,
tutorials and sample programs, but I still have a few questions.
In particular I would like to know more about object life cycles and mem
Hello list
Has anyone considered using the recently available Java foreign
function interface to build Java bindings for GDAL? I am interested
in trying out a Java/GDAL project and would choose to use the FFI over
JNI since this seems like a better supported option for the future.
I would like t
