The mobile version of Vault 3 has been accepted by the Barnes & Noble Nook store.

The following updates have been made to the desktop version of Vault 3:

• Vault 3 now exports photos using multiple threads, resulting in a major speedup and higher exported image quality.
• Vault 3 now supports photos loaded from the Internet.

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 (1.7.0.6), 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?