[ImageJ-bugs] [Bug 899] IJ2 under Vista: very long delay opening image file

[bugzilla at fiji.sc]

http://fiji.sc/bugzilla/show_bug.cgi?id=899

Curtis Rueden <ctrueden at wisc.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |ASSIGNED

--- Comment #7 from Curtis Rueden <ctrueden at wisc.edu> ---
Please file an issue at https://github.com/imagej/imagej-legacy/issues for the
feature request regarding macro interrogation of the SCIFIO status.

As for this bug, I think I found the problem, and I fear it will take some work
to resolve properly. A stack trace during the initial display of a largish
image shows:

"Open..." prio=4 tid=11c85d000 nid=0x128101000 runnable [1280ff000]
   java.lang.Thread.State: RUNNABLE
    at
net.imglib2.display.projector.composite.CompositeXYProjector.map(CompositeXYProjector.java:193)
    at
net.imagej.display.DefaultDatasetView.rebuild(DefaultDatasetView.java:401)
    - locked <6d1c538f8> (a net.imagej.display.DefaultDatasetView)
    at
net.imagej.display.DefaultImageDisplay.rebuild(DefaultImageDisplay.java:136)
    at
net.imagej.display.DefaultImageDisplay.display(DefaultImageDisplay.java:274)

This is in the ImageJ2 display layer: it is trying to build a projection of the
image for use in the ImageJ2 UI, even though that UI is inactive. In other
words: ImageJ is doing twice as much work as necessary, rendering both the IJ1
and IJ2 image planes. Furthermore, the IJ2/ImgLib2 rendering layer is very much
unoptimized at the moment, so the (unnecessary!) IJ2 part of that work tanks
performance rather severely, especially with images over 1 MPx.

The proper fix is to render image data on the IJ2 side only as needed to
actually paint pixels. But we'll need another design iteration of the display
architecture (which has numerous problems) in order to accommodate that.

In the meantime, I'll see about putting a hack somewhere to suppress this
undesirable behavior.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-bugs/attachments/20140815/83f89c04/attachment.html>