Xuggler crash using container.open in Windows 7 64 bit

111 views
Skip to first unread message

juangon

unread,
Aug 5, 2016, 7:33:48 AM8/5/16
to xuggler-users
Hi!

I've faced this problem before, but after some searches I read this issue should be fixed in Xuggler 5.5. Crash log is this:


Stack: [0x00000000023f0000,0x00000000024f0000],  sp=0x00000000024ee0c0,  free space=1016k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [xuggle1171996768527201848.dll+0x773150]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  com.xuggle.xuggler.XugglerJNI.IContainer_open__SWIG_0(JLcom/xuggle/xuggler/IContainer;Ljava/lang/String;IJLcom/xuggle/xuggler/IContainerFormat;)I+0
j  com.xuggle.xuggler.IContainer.open(Ljava/lang/String;Lcom/xuggle/xuggler/IContainer$Type;Lcom/xuggle/xuggler/IContainerFormat;)I+15
j  com.xuggle.xuggler.IContainer.open(Ljava/io/RandomAccessFile;Lcom/xuggle/xuggler/IContainer$Type;Lcom/xuggle/xuggler/IContainerFormat;)I+7
j  com.liferay.portlet.documentlibrary.util.LiferayConverter.openContainer(Lcom/xuggle/xuggler/IContainer;Ljava/lang/String;Z)V+110
j  com.liferay.portlet.documentlibrary.util.LiferayVideoConverter.doConvert()V+24
j  com.liferay.portlet.documentlibrary.util.LiferayVideoConverter.convert()V+1
j  com.liferay.portlet.documentlibrary.util.VideoProcessorImpl$LiferayVideoProcessCallable.call()Ljava/lang/String;+72
j  com.liferay.portlet.documentlibrary.util.VideoProcessorImpl$LiferayVideoProcessCallable.call()Ljava/io/Serializable;+1
j  com.liferay.portal.kernel.process.ProcessExecutor.main([Ljava/lang/String;)V+177
v  ~StubRoutines::call_stub

And code is something like this:

RandomAccessFile randomAccessInputFile = new RandomAccessFile(new File(url), "r");
int value = iContainer.open(randomAccessInputFile, IContainer.Type.READ, null);

I've tried opening container using just the file URL, a FileInputStream, etc with no success. This problem can only be reproduced in Windows 64 bits, is working great in other platforms.

To my surprise, I've compiled latest Xuggle from github for Windows 64 bits using those great instructions using Ubuntu 11 32 bits, and checked that, unfortunately, issue still exists with that version.

There are people asking same issue as mine, with no answers. Do you know how to fix this weird issue? I've tried using Xuggler jar compiled with GCC 4.4 and GCC 4.6, may I have to compile using gcc 4.2?

Thanks very much in advance!

juangon

unread,
Aug 25, 2016, 12:06:42 PM8/25/16
to xuggler-users
FYI, I fixed this behavior by NOT using asm optimizations when compiling Xuggler (setting env variable VS_DEBUG to 1 then compiling).

Seems those optimizations for ffmpeg in Windows 64 bit were causing these failures.
Reply all
Reply to author
Forward
0 new messages