The following updates have been made to the desktop version of Vault 3:
For the Java developers: Vault 3 previously used SWT image scaling which did not support multiple threads. It now uses imscalr to scale images for export. The image export code also uses the Java ImageIO class to load images.
On my 64-bit Windows machine, running the latest Oracle JVM (22.214.171.124), ImageIO.read uses an excessive amount of memory. It's not a memory leak per se, but during the image export process I can see the memory utilization go way up, until it hits a threshold, and then it never goes back down, even after GC has occurred.
Do any of you know of satisfactory alternatives to ImageIO.read?
|EBTCalc Users: A Desktop Version is Now Available!||October 25, 2019|
|Python Script to Audit MediaMonkey Transcoding||August 15, 2019|
|How to decompile Java code with JetBrains IntelliJ IDEA (2018.2.3, Windows 10)||October 5, 2018|
|Java Programming Tip: SWT Photo Frame Program||October 31, 2016|
|Vault 3 (Desktop) Version 1.63 Released||September 9, 2016|
|"Compliance with Court Orders Act of 2016"||April 9, 2016|
|Disable "Visual Voicemail" on Android / T-Mobile||January 17, 2016|