[jira] [Commented] (TIKA-3124) .MOV file crashes Tika app, causes exception on server

["Tim Allison (Jira)" <ji...@apache.org>]

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

Tim Allison commented on TIKA-3124:
-----------------------------------

This is weird.   I think the server and app are having different issues.

 

If I run the app with 'java -Xmx512m -jar tika-app-1.24.1.jar' on linux, I get a logged error "ERROR UnknownBox\{type=} might have been truncated by file end. bytesRead=18940 contentSize=339743992", but no OOM.  However, when I go to the Recursive Json output, I see :
{noformat}

Error during stream reset.
There's a limit of 20971520 bytes for this type of processing in the GUI.
Try the app with command line argument of -J. {noformat}
 

I do get an OOM with -Xmx256m.

 

I get the same behavior when I run "java \-jar tika-app-1.24.1.jar CT-MOV.mov", no OOM at 512m, but an OOM at 256m.--

> .MOV file crashes Tika app, causes exception on server
> ------------------------------------------------------
>
>                 Key: TIKA-3124
>                 URL: https://issues.apache.org/jira/browse/TIKA-3124
>             Project: Tika
>          Issue Type: Bug
>          Components: app, server
>    Affects Versions: 1.24.1
>         Environment: Windows 7 OS
> Java:
> java version "1.8.0_211"
> Java(TM) SE Runtime Environment (build 1.8.0_211-b12)
> Java HotSpot(TM) Client VM (build 25.211-b12, mixed mode)
> Run commands:
> app:  java -jar tika-app-1.24.1.jar
> server:  java -jar tika-server-1.24.1.jar -h localhost -p 5656
>            Reporter: Patrick Maloney
>            Priority: Major
>         Attachments: CT-MOV.mov, appoutput.txt, serveroutput.txt
>
>
> Under 1.24.1, I have some issues with the attached CT-MOV.mov file.
> Dragging it on to the 1.24.1 app causes exception "java.lang.OutOfMemoryError: Java heap space".  See attached file appoutput.txt for full text of exception.  Increasing the max heap size up to 2GB does not fix this.
> Passing the file to the /meta/Content-Type uri on the 1.24.1 server results in a different exception.  See attached file serveroutput.txt.
> Using 1.24 versions of app and server, these problems do not occur.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)