[ 
https://issues.apache.org/jira/browse/TIKA-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829947#comment-15829947
 ] 

Hudson commented on TIKA-2244:
------------------------------

SUCCESS: Integrated in Jenkins build tika-2.x #204 (See 
[https://builds.apache.org/job/tika-2.x/204/])
TIKA-2244 --  be more parsimonious with BufferedInputStream via Josh (tallison: 
rev 78828176a5da851c555f09688075983dfe4d8e49)
* (edit) tika-core/src/main/java/org/apache/tika/io/TikaInputStream.java
* (edit) 
tika-parser-modules/tika-parser-package-module/src/main/java/org/apache/tika/parser/pkg/PackageParser.java
* (edit) CHANGES.txt
* (edit) 
tika-parser-modules/tika-parser-multimedia-module/src/main/java/org/apache/tika/parser/audio/MidiParser.java
* (edit) 
tika-parser-modules/tika-parser-package-module/src/main/java/org/apache/tika/parser/pkg/CompressorParser.java
* (edit) 
tika-parser-modules/tika-parser-office-module/src/main/java/org/apache/tika/parser/wordperfect/WPInputStream.java


> excessive memory usage when parsing a large nested package file
> ---------------------------------------------------------------
>
>                 Key: TIKA-2244
>                 URL: https://issues.apache.org/jira/browse/TIKA-2244
>             Project: Tika
>          Issue Type: Bug
>          Components: core, parser
>    Affects Versions: 2.0
>            Reporter: Joshua Hight
>            Priority: Minor
>
> When parsing large nested files(a couple good examples are maven jars and git 
> objects), a large number of BufferedInputStreams get generated taking up 
> large amounts of memory with their buffers. Upon looking through the relevant 
> code I saw that many of these allocations were coming from 
> TikaInputStream.get(InputStream, TemporaryResources)
> which checks if the InputStream is a BufferedInputStream or 
> ByteArrayInputStream in order to determine whether on not mark is supported. 
> Unfortunately it is common practice to wrap InputStreams in 
> CloseShieldInputStreams, causing it to fail even if mark is in fact supported.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to