Thank you for reporting this error. I saw a similar error to what you are describing recently, and a fix was released.

So first question: have you updated Fiji recently? If not, please call "Help - Update Fiji" to get the latest version of all packages.

>Hello Sapristi,
>yes, my Fiji says it is up to date (as per automatic update).
>In advanced mode of the updater though, the following items
>show as uninstalled :
>SIOX plugin
>RATS plugin
>fiji-lib.jar
>weka.jar
>Why these are not installed, i have no clue. Would these solve my problem?


I have no clue either, for I don't have any Windows machine to test on. If anything, these jar files should be installed. weka.jar is a dependency of TrakEM2--perhaps its absence is causing problems.
Please check if the weka.jar really isn't in the Fiji.app/jars/ folder.

Please reply to the bug report at bugzilla webpage, otherwise I may overlook it.

Thank you for following up.
Sorry for not using the bugzilla webpage for the last communication (attached below)
I installed weka.jar and fiji-lib.jar and no improvement.
I then noticed that after starting 3dViewer I have an error message in System-Log that reads: \\fileserver\profiles$\Desktop\.ImageJ_3D_Viewer.props (Zugriff verweigert)
Now i searched for files named "ImageJ_3D_Viewer.props" but i did not find any.
Any hints?

> Hello Sapristi,
> >yes, my Fiji says it is up to date (as per automatic update).
> >In advanced mode of the updater though, the following items
> >show as uninstalled :
> >SIOX plugin
> >RATS plugin
> >fiji-lib.jar
> >weka.jar
> >Why these are not installed, i have no clue. Would these solve my problem?


I have no clue either, for I don't have any Windows machine to test on. If
anything, these jar files should be installed. weka.jar is a dependency of
TrakEM2--perhaps its absence is causing problems.
Please check if the weka.jar really isn't in the Fiji.app/jars/ folder.

Please reply to the bug report at bugzilla webpage, otherwise I may overlook
it.

Just a wild shot in the dark (I do not have enough information to make an educated guess): maybe the object you are trying to visualize is very, very large? Or your graphics adapter has little texture memory? That would explain the freeze after a delay.

Hello Johannes,
I just tried with the ImageJ Sample "Bat Cochlea" scaled up by 2x. Now that is really not such a big structure. After using 'Show as Volume' which started the 3d_viewer i got no content in the viewer window but this error message in the Log:
ERROR:
java.lang.IllegalArgumentException: Argument out of range: 1

	at ij.ImageStack.getPixels(ImageStack.java:159)

	at ini.trakem2.persistence.FSLoader.fetchImage(FSLoader.java:479)

	at ini.trakem2.persistence.FSLoader.fetchImagePlus(FSLoader.java:449)

	at ini.trakem2.imaging.PatchStack$VirtualStack.getPixels(PatchStack.java:681)

	at ij3d.Volume$ByteLoader.<init>(Volume.java:238)

	at voltex.VoltexVolume$ByteLoader.<init>(VoltexVolume.java:368)

	at voltex.VoltexVolume.initLoader2(VoltexVolume.java:163)

	at voltex.VoltexVolume.<init>(VoltexVolume.java:102)

	at voltex.VoltexVolume.<init>(VoltexVolume.java:68)

	at voltex.VolumeRenderer.<init>(VolumeRenderer.java:72)

	at voltex.VoltexGroup.<init>(VoltexGroup.java:72)

	at ij3d.Content.displayAs(Content.java:119)

	at ij3d.Image3DUniverse.addContent(Image3DUniverse.java:506)

	at ij3d.Image3DUniverse.addVoltex(Image3DUniverse.java:572)

	at ini.trakem2.display.Display3D.showVolume(Display3D.java:569)

	at ini.trakem2.display.Display$22.run(Display.java:3977)

	at ini.trakem2.utils.Dispatcher$Task.run(Dispatcher.java:46)

	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

	at java.util.concurrent.FutureTask.run(FutureTask.java:138)

	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

	at java.lang.Thread.run(Thread.java:619)
Does this explain anything?

Christian, this bug is in trakem2 as your Exception stack trace indicates. I will fix it after March 1st -- hard deadline for a grant application.

Albert, was this fixed yet?

(In reply to comment #7)
> Albert, was this fixed yet?


As far as I know it is fixed.