<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Lizard inference engineering: Prove a process really exited]]></title><description><![CDATA[<p dir="auto"><strong>Inference Engineering · Day 8 · Evening</strong></p>
<p dir="auto"><img src="https://lizard-llm.qendryx.com/screenshots/Benchmark/Screenshot%202026-07-22%20214040.png" alt="Benchmark command center — lizard-llm.qendryx.com" class=" img-fluid img-markdown" /></p>
<p dir="auto">A process ID is not enough to prove process identity.</p>
<p dir="auto">Windows can recycle a PID after a model worker exits. If cleanup logic trusts the number alone, it may block on an unrelated process—or terminate the wrong one.</p>
<p dir="auto">Lizard records PID plus start time and verifies the descendant tree before declaring model memory released. A crashed worker becomes recoverable without making cleanup reckless.</p>
<p dir="auto">Inference reliability includes the process lifecycle around the kernel.</p>
<p dir="auto"><strong>Engineering fact:</strong> Lizard tracks process identity using PID plus start time so a recycled Windows PID is not mistaken for the old model process.</p>
<p dir="auto"><a href="https://lizard-llm.qendryx.com/docs.html" rel="nofollow ugc">Read the relevant Lizard page</a></p>
<p dir="auto">#WindowsEngineering #ReliabilityEngineering #ProcessManagement #LocalAI #LizardLLM</p>
<p dir="auto">&lt;!-- lizard-marketing-slot:day-08-pm --&gt;</p>
]]></description><link>https://community.lizard-llm.qendryx.com/topic/55/lizard-inference-engineering-prove-a-process-really-exited</link><generator>RSS for Node</generator><lastBuildDate>Mon, 24 Aug 2026 01:33:36 GMT</lastBuildDate><atom:link href="https://community.lizard-llm.qendryx.com/topic/55.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 31 Jul 2026 11:00:11 GMT</pubDate><ttl>60</ttl></channel></rss>