[
https://issues.apache.org/jira/browse/TIKA-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491376#comment-15491376
]
Tim Allison edited comment on TIKA-2058 at 9/14/16 8:37 PM:
------------------------------------------------------------
-[~comcortim], given that you're hitting FileBackedDataSource, I assume you're
running into this with an attachment, not with the original MSG, because you're
reading that with an InputStream. Would you be able to share your code for
processing the attachments that you're spooling to the file system?- Never
mind. After more kicking of tires, I think [~lfcnassif]'s patch should work.
was (Author: [email protected]):
[~comcortim], given that you're hitting FileBackedDataSource, I assume you're
running into this with an attachment, not with the original MSG, because you're
reading that with an InputStream. Would you be able to share your code for
processing the attachments that you're spooling to the file system?
> Memory Leak in Tika version 1.13 when parsing millions of files
> ---------------------------------------------------------------
>
> Key: TIKA-2058
> URL: https://issues.apache.org/jira/browse/TIKA-2058
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.13
> Reporter: Tim Barrett
> Attachments: Yourkit screenshot.png, poi-3.15-beta1-p1.jar,
> poi-3.15-beta1-p1.pom, prevents-OOM-when-writable-is-false.patch,
> screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> We have an application using Tika which parses roughly 7,000,000 files of
> different types, many of the files are MSG files with attachments. This works
> correctly with Tika 1.9, and has been in production for over a year, with
> parsing runs taking place every few weeks. The same application runs into
> insufficient memory problems (java heap) when using Tika 1.13.
> I have used lsof and file leak detector to track down open files, however
> neither shows any open files when the application is running. I did find an
> issue with open files https://issues.apache.org/jira/browse/TIKA-2015,
> however there was a workaround for this and this is not the issue.
> I am sorry to have to report this with a level of vagueness, but with lsof
> turning nothing up I am a bit stuck as to how to investigate further. We are
> more than willing to help by testing on the basis of any ideas provided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
