[OpenJDK 2D-Dev] sun.java2D.pisces big memory usage (waste ?)

Andrea Aime andrea.aime at geo-solutions.it
Thu Mar 28 20:40:47 UTC 2013

On Thu, Mar 28, 2013 at 8:38 PM, Phil Race <philip.race at oracle.com> wrote:

> Maintaining a pool of objects might be an appropriate thing for an
> applications,
> but its a lot trickier for the platform as the application's usage pattern
> or intent
> is largely unknown. Weak references or soft references might be of use but
> weak references usually go away even at the next incremental GC and soft
> references tend to not go away at all until you run out of heap.

At the same time, the current decision is affecting some applications badly.
I've seen the same happening for another old java2d bug, where the alpha
tile is cached and coordinated with JVM synchronized statement that kill
scalability in
server side applications heavily using Java2D (e.g, map servers):

For these kinds of decisions sometimes it's not possible to find a one size
fits all: it would be good if there was some way for the application to
plug-in their
own behavior, ideally with a Graphics2D rendering hint, less ideally with a
variable (a JVM can run multiple applications, not all might have the same

Now, I understand that today (java 7 or java 8) one could plug-in their own
yet writing a rasterizer from scratch is kind of a tall order.
Being able to get some control on these kind of decisions via hints would
be nicer imho.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/2d-dev/attachments/20130328/7ec89aba/attachment.html>

More information about the 2d-dev mailing list