I think the problems is "created" in
SVGElementImageBridge#createImageGraphicsNode
The image file is opened at a certain point
reference = openStream(e, purl);
There is also a try-finally block that seems to close it again
(reference.release()), but there are multiple returns from that function
that do not invoke the release call, like in
// It's a bouncing baby Raster...
return createRasterImageNode(ctx, e, img, purl);
I added the release invocations and recompiled. The rendering still seems to
work and now the image file no longer stays locked.
Should I submit a bug for this, or is this intentional ?
Thanks,
Peter
Peter Coppens wrote:
>
> I am attaching ( http://www.nabble.com/file/p11471903/FopLock.java
> FopLock.java ) a little repro.
>
> Anyone seen this before? Any tips on how I could avoid this?
>
> Many thanks,
>
> Peter
>
>
>
>
>
> Peter Coppens wrote:
>>
>> Gentlepeople,
>>
>> I am using batik through fop in a servlet. I have the impression that
>> referenced image files through the svg:image tag are kept open after
>> being rendered (while I would want to remove the files).
>>
>> I see similar behavior with squiqle - once an svg file is displayed that
>> references an image the image file seems to be locked even though the svg
>> file that reference that image file is no longer displayed.
>>
>> Is that known/intentional behavior? Is there any way to avoid that ?
>>
>> Thanks,
>>
>> Peter
>>
>
>
--
View this message in context:
http://www.nabble.com/svg%3Aimage---referred-images-kept-open--tf4026380.html#a11473661
Sent from the Batik - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
