Hi Christophe,
it seems that downgrading to Java 1.5 won't solve the problem
completely.
I tried the following macro (with 8 2048x2048 images, 8-bit)
under OS X 10.4.10, 2.1 GHz PowerPC 5, 1680*1050 screen,
today's ImageJ 1.39f, Java 1.5.0_07; 256 MB assigned to ImageJ:
run("Blobs (25K)");
run("Size...", "width=2048 height=2048 interpolate");
run("Duplicate...", "title=blobs-1.gif");
run("Duplicate...", "title=blobs-2.gif");
run("Duplicate...", "title=blobs-3.gif");
run("Duplicate...", "title=blobs-4.gif");
run("Duplicate...", "title=blobs-5.gif");
run("Duplicate...", "title=blobs-6.gif");
run("Duplicate...", "title=blobs-7.gif");
for (i=0; i<10; i++) {
run("Tile");
run("Cascade");
}
After running the macro, the text menu was still there (when
clicking into the macro text window), but everything was dead
for about 45 seconds after running the macro. Commands selected
from the text menu bar (after clicking into the macro text window)
are executed only after that time (the dialog box comes up
thereafter), switching to the Image menus in the menu bar does
not work when clicking on an image (the menus are missing) and
refresh of the image windows does not happen.
After that time, everything is fine again.
It seems that the delay time is roughly proportional to the
number of "tile" and "cascade" commands, so ImageJ recovers
after about 7 seconds when running the loop for i<2 instead
of i<10.
Michael
________________________________________________________________
On 2 Oct 2007, at 10:31, Christophe Leterrier wrote:
> Dear all,
>
> I'd like to report a problem with the "Tile" command (for tiling
> windows) under OSX 10.4.10, ImageJ 1.39f, Java 1.6dp, 20' iMac
> Core2Duo at 1680*1050.
> Often when you tile a reasonable number of windows (I just got it
> with six 2048x2048 8-bit images), ImageJ crashes and the
> application suddenly quits.
>
> It is not totally reproducible, meaning that it can happen or not
> with the same group of windows open, but it happens often enough to
> make the use of tiling a real hassle. Do anybody have the same
> problem ? Do you have a clue on what could be wrong and how to
> correct it (I'd prefer not to downgrade to Java 1.5, as 1.6 is much
> faster).
>
> Thanks a lot,
>
> Christophe Leterrier
Locked
