Thanks Devin.  It occurred to me to do something similar but it is possible for my app to be running simultaneous OCR jobs.  Killing all of them could end up shutting down something important.  If there was a way to get the process id when the job starts, that might solve the problem for now.

@Robert, yes I am actually testing with a very simple workflow which search under a folder then for each document to do an OCR with the SDK script as following:

    // Wrapper class that puts an OcrEngine back in the pool when it is no longer needed
    class OcrEngineWrapper : IDisposable
    {
        public OcrEngine OcrEngine { get; private set; }

        public OcrEngineWrapper(OcrEngine ocrEngine)
        {
            this.OcrEngine = ocrEngine;
        }

        public void Dispose()
        {
            if (this.OcrEngine != null)
                OcrEngineManager.ReleaseEngine(this.OcrEngine);
        }
    }

    // Manager class that keeps a pool of available OcrEngines
    class OcrEngineManager
    {
        static Queue<OcrEngine> _ocrEnginePool = new Queue<OcrEngine>();
        public static OcrEngineWrapper GetOcrEngine()
        {
            lock (_ocrEnginePool)
            {
                if (_ocrEnginePool.Count > 0)
                    return new OcrEngineWrapper(_ocrEnginePool.Dequeue());
            }

            return new OcrEngineWrapper(OcrEngine.LoadEngine());
        }

        public static void ReleaseEngine(OcrEngine ocrEngine)
        {
            lock (_ocrEnginePool)
            {
                _ocrEnginePool.Enqueue(ocrEngine);
            }
        }
    }


    /// <summary>
    /// Provides one or more methods that can be run when the workflow scripting activity is performed.
    /// </summary>
    public class Script1 : RAScriptClass102
    {
        /// <summary>
        /// This method is run when the activity is performed.
        /// </summary>
        protected override void Execute()
        {
            SetActivityTokenValue("SDK_Warning", "");

            var docinfo = this.BoundEntryInfo as DocumentInfo;

            try
            {
                using (OcrEngineWrapper ocrEngine = OcrEngineManager.GetOcrEngine())
                {
                    ocrEngine.OcrEngine.Run(docinfo);
                }
            }
            catch(Exception ex)
            {
                string errormessage = ex.Message;
                SetActivityTokenValue("SDK_Warning", errormessage);
            }
            finally
            {


            }
        }
    }

And by running that workflow again and again (twice or 3 times) then I see more than 4 instances stays in memory.

When you said it's been fix for Client 10.4.1, does it also being fixed for SDK call? Thanks.

Hi,

Our customer sees a related problem with multiple spawning NuanceLS.exe processes with OmniOCR18.5 also using SDK to store in Laserfiche

Is there a fix for version 10.3.1?

many thanks