The project contains patches of relatively large sizes 16k^2 to 32k^2 px.  These sizes being far smaller than the known upper limit of ~45^2 px for a single ImageJ ImageProcessor, all internal rendering operations function perfectly.  The images can be deformed and mipmaps can be generated---that is they can be rendered at 100% scale by ImageJ and the mpicbg library.  When I now try to view these images at a zoom factor >50% (e.g. 75% or 100%), it happens that the result is completely scrambled.  Scrambling includes that an arbitrary region of the image at much lower zoom appears or that weird stripy patterns are painted.  Sometimes, the correct region is rendered correctly.  This does not depend on the region, by switching between slices, different incarnations of the effect can be observed.  No error is printed, the computer has sufficient amount of memory and disc space.

The effect is the same when I try to export a region at 100% resolution which makes it impossible to export that project for CATMAID or for other visualizations.

Mipmaps were saved as rag---can that be an issue?  Does rag have an upper limit of bytes for compression?  Is it an AWT problem with larger images?  I observed the problem already with the smaller images of 16k^2 px.