| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Thank you. I will take a look. Also, how well does the master branch work for you? The release process got stalled, but we are due for a breaking release. I'm targeting August 7th for merging and release. Please ping me if not released by then. |
Sorry, something went wrong.
|
These are the results when I build and test the repository, see output.txt. I'm running on Julia 1.8.5 and Windows 10. |
Sorry, something went wrong.
|
@mkitti What's the status on the release? |
Sorry, something went wrong.
|
I will arrange for it today. |
Sorry, something went wrong.
|
I'm trying to include #165 . Almost there. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
It was observed that JavaCall was leaking memory when getting arrays of objects from Java. This is due to the fact that arrays from Java are converted into Julia arrays by copying the elements over from the Java array, but the Java array is subsequently not freed from memory, causing a leak as at the end of the Julia code the pointer is garbage collected. In #135 essentially the same leak was fixed, but only for primitive arrays, not arrays of Java objects, etc. This PR aims to solve the issue for the remaining cases.