-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGABRT for FITS web service on MOV file #219
Comments
I tested PR209 locally. It appears to work in general, but has not resolved this particular problem. Its possible some later version of libmediainfo has a bug fix, since 209 is close to a year old. When running #209 I did get responses from the server which contained the failure, which was a new behavior. It looks like it may be a memory allocation problem with libmediainfo when multiple scans are running in the same jvm. I actually got 3 different error messages back. The first was:
The other two were similar, with the following top level messages:
|
@bbpennel Have tried running MediaInfo directly on the file? |
I think I may have at the time, but it was probably whatever version was bundled with FITS. I could try it again once a new version of FITS is released with #209 included. |
We are running into a case where a particular .mov file is causing the jetty instance running the FITS web service to crash. However, it only causes this crash if the web service is processing other file as the same time. The .mov itself is ~250mb, while the jetty instance has -Xmx2g so it seems unlikely it is maxing out memory. To be safe I tried doubling the max heap, but had the same problem.
The logs from jetty don't show anything at the time of the crash, and if I enable a heap dump for running out of memory it does not perform the dump. We do see this error in the FITS log:
This is happening with FITS version 1.5.0 and the web service at version 1.2.1.
Its also worth noting that I can process the same file multiple times concurrently with the FITS CLI with no problems. But If I do the same thing with the web service it dies. All requests to the server get empty responses.
We do get a core backtrace from system logs, which mostly lists a lot of waiting threads, but does show one thread where libmediainfo is getting aborted:
This is being performed with the libmediainfo.so file that comes with FITS, which appears to be from 2015. We tried updating to a current version libmediainfo, but it seemed like FITS didn't know how to interact with it, so we'd see
<tool toolname="MediaInfo" toolversion="21.03" status="failed" />
in the result. Judging by the regular output, it looks like FITS ships with version0.7.75
. The version we install were rpms from rhel, I'm not sure what the original source of the files that ship with FITS is.The text was updated successfully, but these errors were encountered: