commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Moerchen (Updated) (JIRA)" <>
Subject [jira] [Updated] (SANSELAN-63) Audit and fix resource leaks
Date Sat, 18 Feb 2012 13:20:59 GMT


Adrian Moerchen updated SANSELAN-63:

    Attachment: finbugs.patch

I've recommend you to use Findbugs. I've attached a patch for you {{pom.xml}}. After applying
the patch you can run {{mvn site}}. This will also generate the Findbugs analyses. There you
can search for *OS_OPEN_STREAM* to find possible candidates where stream may left be open.

For developent you could add Findbugs to Eclipse or whatever you use.


Btw. Is there a release date for the next version?
> Audit and fix resource leaks
> ----------------------------
>                 Key: SANSELAN-63
>                 URL:
>             Project: Commons Sanselan
>          Issue Type: Bug
>    Affects Versions: 0.97
>         Environment: Windows 7, Java, 0.97-Incubator
>            Reporter: Adrian Moerchen
>         Attachments: 380440_295155317172029_185275861493309_985773_37867068_n.bmp, finbugs.patch
> The attached image is somehow corrupt (it still can be opened with IrfanView).
> Trying to read the image information with {{Sanselan.getImageInfo(file)}} results in
an IOException.
> After this the image is still locked on the file system, and can't be deleted for example.
I expected it to be immediately get unlocked on the file system, after the error occured.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message