A custom script that uses Snappy to apply orbit files to many Sentinel 1 products sometimes crashes with a fatal JRE error, such as the following:
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007f14eff62f1e, pid=1443, tid=139727907419968
JRE version: Java™ SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27)
Java VM: Java HotSpot™ 64-Bit Server VM (25.60-b23 mixed mode linux-amd64 compressed oops)
C [libpython2.7.so.1.0+0xadf1e] type_dealloc+0xfe
Failed to write core dump. Core dumps have been disabled. To enable core dumping, try “ulimit -c unlimited” before starting Java again
An error report file with more information is saved as:
If you would like to submit a bug report, please visit:
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
Aborted (core dumped)
The script will always fail with the same products (provided the same set of inputs are given). However, it is likely that these products are not faulty, as they will process correctly running through SNAP (GUI), and will even run through the script correctly if a different set of inputs are given. I do not believe that the script is at fault either, as it can successfully process products without fault with certain inputs.
e.g. The error occurs when during/after reading S1A_IW_GRDH_1SDV_20150206T173846_20150206T173911_004506_00587B_70ED.SAFE.zip, after having applied an orbit file to multiple other products. However, running this file through the script by itself, or will fewer additional products, does not result in this crash.
Additionally, it does not appear that the problem is resulting from not finding an appropriate orbit file, and is not related to a lack of memory.
Does anyone know why this might be occurring?