Thanks very much to both you and Chris. I managed to work around the
problem, but I think something like what you suggest would have helped.
I'm also thinking the problem may have been on my side, so I don't think
a test case will help. We'll see.
Nick
On Wed, 2002-08-14 at 14:01, Chet Haase wro
There is also a trick to recreating large objects which
could influence your app:
The code:
BufferedImage img;
while (true) {
img = new BufferedImage(w, h, type);
}
will use up more memory in general than the following:
BufferedImage img;
Hi Nick,
In general it's best to avoid recreating BufferedImages in an animation
loop, but it sounds like you only do it when necessary, which is okay.
I'm interested to see why you need to make a larger BufferedImage when
you "zoom in". If you send me a small testcase that reproduces the
proble
Hi,
I think I'm seeing a problem with creating BufferedImage-s and memory
use. To over simplify a bit I'm using one to draw on as part of some
animation. Sometimes I need to recreate it when I've zoomed in (the
BufferedImage needs to become bigger). If I do this enough I eventually
I get an OutOf
Jesse,
Funny you mention that - I've been spending the last few days
of my life on that exact problem.
This is a bug in 1.4 (and 1.4.1) in our multithreaded approach
to fullscreen and display mode functionality. I am working on
a fix for it that seems to be mostly functional. Given the
timefra
I'm trying to figure out how to alt-tab (using windows) out of, and then back
into a java application this is running in fullscreen mode. When i try to do
this with either of the examples that come with the fullscreen mode tutorial:
http://java.sun.com/docs/books/tutorial/extra/fullscreen
