You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Hong-Thai Nguyen (JIRA)" <ji...@apache.org> on 2013/07/23 17:30:49 UTC
[jira] [Updated] (TIKA-1152) Process loops infinitely on parsing of
a CHM file
[ https://issues.apache.org/jira/browse/TIKA-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hong-Thai Nguyen updated TIKA-1152:
-----------------------------------
Summary: Process loops infinitely on parsing of a CHM file (was: Process stucks on parsing of a CHM file)
> Process loops infinitely on parsing of a CHM file
> -------------------------------------------------
>
> Key: TIKA-1152
> URL: https://issues.apache.org/jira/browse/TIKA-1152
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.4
> Environment: Windows/Linux
> Reporter: Hong-Thai Nguyen
> Priority: Critical
> Fix For: 1.5
>
> Attachments: eventcombmt.chm
>
>
> By parsing [the attachment CHM file|^eventcombmt.chm] (MS Microsoft Help Files), Java process stuck.
> {code}
> Thread[main,5,main]
> org.apache.tika.parser.chm.lzx.ChmLzxBlock.extractContent(ChmLzxBlock.java:203)
> org.apache.tika.parser.chm.lzx.ChmLzxBlock.<init>(ChmLzxBlock.java:77)
> org.apache.tika.parser.chm.core.ChmExtractor.extractChmEntry(ChmExtractor.java:338)
> org.apache.tika.parser.chm.CHMDocumentInformation.getContent(CHMDocumentInformation.java:72)
> org.apache.tika.parser.chm.CHMDocumentInformation.getText(CHMDocumentInformation.java:141)
> org.apache.tika.parser.chm.CHM2XHTML.process(CHM2XHTML.java:34)
> org.apache.tika.parser.chm.ChmParser.parse(ChmParser.java:51)
> org.apache.tika.parser.ParserDecorator.parse(ParserDecorator.java:91)
> org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:242)
> org.apache.tika.parser.AbstractParser.parse(AbstractParser.java:53)
> com.polyspot.document.converter.DocumentConverter.realizeConversion(DocumentConverter.java:192)
> ...
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira