ili2fme Writer Crashes After Previous Job Fails

Hi everyone,

I’m seeing a reproducible crash in FME Server when using the ili2fme Writer.

Environment:

• FME Flow 2024.2.3 (Windows Server) also happening with FME Flow 2025.2.

• ArcGIS Server 11.4 on the same machine

• Nightly scheduled jobs (~50) using ili2fme Writer to validate and export INTERLIS data

Problem:

• A job that fails with model validation errors finishes correctly.

• The next job in the same FME Engine process crashes with EXCEPTION_ACCESS_VIOLATION (native code), engine restarts automatically.

2

Thu-27-Nov-2025 02:02:24.622 AM   INFORM   Thread-20   localhost_Engine1   Emptying factory pipeline
Thu-27-Nov-2025 02:02:25.271 AM   INFORM   Thread-20   localhost_Engine1   FeatureReader_18 (QueryFactory): 1 input initiators processed
Thu-27-Nov-2025 02:02:26.032 AM   INFORM   Thread-20   localhost_Engine1   FeatureReader_16 (QueryFactory): 1 input initiators processed
Thu-27-Nov-2025 02:02:26.837 AM   INFORM   Thread-20   localhost_Engine1   FeatureReader_15 (QueryFactory): 1 input initiators processed
Thu-27-Nov-2025 02:02:27.773 AM   INFORM   Thread-20   localhost_Engine1   FeatureReader_12 (QueryFactory): 1 input initiators processed
Thu-27-Nov-2025 02:02:28.646 AM   INFORM   Thread-20   localhost_Engine1   FeatureReader_11 (QueryFactory): 1 input initiators processed
Thu-27-Nov-2025 02:02:29.468 AM   INFORM   Thread-20   localhost_Engine1   FeatureReader_3 (QueryFactory): 1 input initiators processed
Thu-27-Nov-2025 02:02:30.255 AM   INFORM   Thread-20   localhost_Engine1   FeatureReader_4 (QueryFactory): 1 input initiators processed
Thu-27-Nov-2025 02:02:31.216 AM   INFORM   Thread-20   localhost_Engine1   FeatureReader_7 (QueryFactory): 1 input initiators processed
Thu-27-Nov-2025 02:02:32.611 AM   INFORM   Thread-20   localhost_Engine1   #
Thu-27-Nov-2025 02:02:32.611 AM   INFORM   Thread-20   localhost_Engine1   # A fatal error has been detected by the Java Runtime Environment:
Thu-27-Nov-2025 02:02:32.611 AM   INFORM   Thread-20   localhost_Engine1   #
Thu-27-Nov-2025 02:02:32.611 AM   INFORM   Thread-20   localhost_Engine1   #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000042c3a8f5, pid=24324, tid=13680
Thu-27-Nov-2025 02:02:32.611 AM   INFORM   Thread-20   localhost_Engine1   #
Thu-27-Nov-2025 02:02:32.611 AM   INFORM   Thread-20   localhost_Engine1   # JRE version: OpenJDK Runtime Environment Temurin-17.0.12+7 (17.0.12+7) (build 17.0.12+7)
Thu-27-Nov-2025 02:02:32.611 AM   INFORM   Thread-20   localhost_Engine1   # Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.12+7 (17.0.12+7, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
Thu-27-Nov-2025 02:02:32.611 AM   INFORM   Thread-20   localhost_Engine1   # Problematic frame:
Thu-27-Nov-2025 02:02:32.619 AM   INFORM   Thread-20   localhost_Engine1   # C  0x0000000042c3a8f5
Thu-27-Nov-2025 02:02:32.619 AM   INFORM   Thread-20   localhost_Engine1   #
Thu-27-Nov-2025 02:02:32.619 AM   INFORM   Thread-20   localhost_Engine1   # Core dump will be written. Default location: C:\ProgramData\Safe Software\FMEFlow\repositories\hs_err_pid24324.mdmp
Thu-27-Nov-2025 02:02:32.619 AM   INFORM   Thread-20   localhost_Engine1   #
Thu-27-Nov-2025 02:02:32.619 AM   INFORM   Thread-20   localhost_Engine1   # An error report file with more information is saved as:
Thu-27-Nov-2025 02:02:32.619 AM   INFORM   Thread-20   localhost_Engine1   # D:\workFME\fmeengines\localhost_Engine1\hs_err_pid24324.log
Thu-27-Nov-2025 02:02:32.764 AM   INFORM   Thread-20   localhost_Engine1   #
Thu-27-Nov-2025 02:02:32.764 AM   INFORM   Thread-20   localhost_Engine1   # If you would like to submit a bug report, please visit:
Thu-27-Nov-2025 02:02:32.764 AM   INFORM   Thread-20   localhost_Engine1   #   https://github.com/adoptium/adoptium-support/issues
Thu-27-Nov-2025 02:02:32.764 AM   INFORM   Thread-20   localhost_Engine1   # The crash happened outside the Java Virtual Machine in native code.
Thu-27-Nov-2025 02:02:32.764 AM   INFORM   Thread-20   localhost_Engine1   # See problematic frame for where to report the bug.
Thu-27-Nov-2025 02:02:32.764 AM   INFORM   Thread-20   localhost_Engine1   #
Thu-27-Nov-2025 02:02:32.766 AM   INFORM   Thread-20   localhost_Engine1   
Thu-27-Nov-2025 02:02:32.766 AM   INFORM   Thread-20   localhost_Engine1   [error occurred during error reporting (), id 0xe06d7363, EXCEPTION_UNCAUGHT_CXX_EXCEPTION (0xe06d7363) at pc=0x00007ffb26f51b39]
Thu-27-Nov-2025 02:02:32.766 AM   INFORM   Thread-20   localhost_Engine1   
Thu-27-Nov-2025 02:02:33.411 AM   INFORM   Thread-20   localhost_Engine1   
Thu-27-Nov-2025 02:02:33.411 AM   INFORM   Thread-20   localhost_Engine1   [error occurred during error reporting (), id 0xc0000005, EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffaee19c580]
Thu-27-Nov-2025 02:02:33.411 AM   INFORM   Thread-20   localhost_Engine1   
Thu-27-Nov-2025 02:02:33.932 AM   WARN     localhost_Engine1   393562 : Process "localhost_Engine1" ended unexpectedly. Being restarted on attempt 1...
Thu-27-Nov-2025 02:02:33.932 AM   WARN     localhost_Engine1   393563 : 

 1) Review the log file for the job that was running when the problem occurred.
 2) Check that the terminated program is not already running on the system.
 3) Check that correct license(s) are in effect.
Thu-27-Nov-2025 02:02:33.932 AM   INFORM   localhost_Engine1   393566 : Process "localhost_Engine1" waiting for process output listener threads to terminate...
Thu-27-Nov-2025 02:02:33.932 AM   INFORM   localhost_Engine1   393569 : Process "localhost_Engine1" closing process stderr output stream
Thu-27-Nov-2025 02:02:33.932 AM   INFORM   localhost_Engine1   393570 : Closed process stderr output stream
Thu-27-Nov-2025 02:02:33.932 AM   INFORM   localhost_Engine1   393567 : Process "localhost_Engine1" closing process stdout output stream
Thu-27-Nov-2025 02:02:33.932 AM   INFORM   localhost_Engine1   393568 : Closed process stdout output stream
Thu-27-Nov-2025 02:02:33.932 AM   INFORM   localhost_Engine1   393500 : Process "localhost_Engine1" raw startup command is: "C:/Program Files/FMEFlow/Server/fme/FMEEngine.exe" REGISTER_FME_ENGINE localhost 7070 DEFAULT "C:/Program Files/FMEFlow/Server/fmeEngineConfig.txt" -ENGINE_HOST_NAME localhost  -ENGINE_TYPE STANDARD -FME_INSTANCE_NAME localhost_Engine1
Thu-27-Nov-2025 02:02:33.932 AM   INFORM   ProcessStateReportListener   393607 : Will wait for 0 seconds for process localhost_Engine1 to start up.

• Last lines from the crashing FME Job 

• No hs_err_pid*.log is created.

• Crash occurs only when the previous job had model errors.

• Temporary workaround: set Job Retry = 1 → next job succeeds, but not ideal.

Has anyone encountered similar ili2fme Writer crashes after previous jobs fail?

Thanks for any guidance!

Shari