<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'><br><blockquote style="border-top-color: rgb(204, 204, 204); border-left-color: rgb(204, 204, 204); border-right-color: rgb(204, 204, 204); border-bottom-color: rgb(204, 204, 204); border-top-width: 1px; border-left-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-top-style: solid; border-left-style: solid; border-right-style: solid; border-bottom-style: solid; padding-top: 7px; padding-right: 7px; padding-bottom: 7px; padding-left: 7px; background-color: rgb(245, 245, 245);"><div> This problem is not about a VM bug, or even a code bug. It's just that Florin found an inconsistency in the state of the image. That inconsistency was introduced a couple years ago and survived unnoticed in the image until now. <br><br>It is one of the peculiarities of having a persistent image: some bugs are not even in the code.<br><br>- Bert -</div></blockquote><br><div>Fascinating. </div><div><br></div><div>That makes sense. </div><div><br></div><div>Analogous to the way class state can introduce bugs, the image itself has state and can introduce a bug.</div></div></body></html>