Java 17 application segfaults while using MATLAB Engine API for Java on Linux

Our application communicates with several instances of MATLAB using the engine API. MATLAB is running in Java 8, our application is being upgraded to run in Java 17. When using MatlabEngine#fevalAsync, the application consistently crashes with a sigsegv (crash dump attached).

I'm aware that MATLAB only supports Java 8 (per similar questions) - and that I'm using a version of MATLAB that predates the release of Java 17 - so I don't expect an easy fix for this problem.

• Is there a timeline for engine.jar to be updated to support newer versions of Java?
• I imagine I'm not the first person to try this: is there a recommended way to work around the issue? Is it reasonable to try to replace engine.jar with calls through MATLAB's REST API? Should we connect to MATLAB from a microservice running in Java 8 and communicating with our main application over a message queue?

[Patrick Conley]

After some brief tests, MATLAB R2022b appears to work with our application - I was using R2019a before. I'll have to test more thoroughly before I decide if I trust it.