Thanks for the feedback,
Running it on jdk1.7.0_21-32bit I don't see that error any more (though I
am still having camera capture issues when integrating LTI CIVIL into JFX -
still trying to narrow down where the fault lies).
I do get this error however, but it seems to recover from it.
java.lan
I take it there's no way to avoid the resources issue in the old JFX,
it's just a plain and simple bug?
I don't know of a way to completely avoid it. As far as we know there
aren't any actual leaks in the more recent FX 2.2.x texture code, but
the resource disposal is not deterministic and i
This is an older version, probably JFX from around jdk1.7.0_02.
I'm running it now on jdk1.7.0_21 to see what happens (takes about an hour
to get to the point of failure, which is why I didn't pick it up when I
wrote the code originally).
Unfortunately chunks of the system are broken when it runs
I missed the fact that this is using the non-public
impl_fromExternalImage() method. This was replaced in FX 2.2 by
SwingFXUtils.toFXImage as Werner mentions and has been removed from FX 8
entirely.
One more thing to check is that jfxImage is non-null, although it is
still more likely than no
Is this from FX 2.2.x or FX 8? The stack trace suggests an earlier
version of FX. The only thing I can think of off hand is that the HW
texture couldn't be created, probably because you ran out of resources.
There are a few issues relating to this, which we believe are fixed in
FX 8 with the im
Is this the same as SwingFXUtils.toFXImage?
On 11.06.2013 14:27, Daniel Zwolenski wrote:
BufferedImage buffImage = AWTImageConverter.toBufferedImage(image);
jfxImage = javafx.scene.image.Image.impl_fromExternalImage(buffImage);
previewView.setImage(jfxImage);
Can anyone tell me what might cause the exception below in Prism?
It's from an app that captures video via a native library (LTI-CIVIL) and
then converts that image to JFX display via:
BufferedImage buffImage = AWTImageConverter.toBufferedImage(image);
jfxImage = javafx.scene.image.Image.
