<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Ha. I think I found something. <span style="font-size: 10pt">See Graphics-mt.514. I am not 100% sure that this was the culprit but I will backport it to Squeak 5.3 just in case.</span><div><br></div><div>Best,</div><div>Marcel</div><blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 27.04.2022 13:37:45 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hi Lauren, hi all --<div><br></div><div>Okay, I give up on this for now. I cannot reliably reproduce the issue.</div><div><br></div><div>My only hypothesis is that we do something wrong with freeing the current Metal texture in sqSqueakOSXMetalView.m:449. Maybe we should tell the Metal framework about this and not just free the pointer... Reading the Metal documentation might help...</div><div><br></div><div>At least, the segfault always occurs in the same situation:</div><div><br></div><div>1. App window size changed.</div><div>2. Morphic ui process detects this via DisplayScreen class>checkForNewScreenSize </div><div>3. The next call to DisplayScreen(Form)>boundingBox triggers a vmIOProcessEvents() in the regular interpreter loop via checkForEventsMayContextSwitch().</div><div>4. A display event will be processed ending up in sqSqueakOSXMetalView loadTexturesSubRectangle:</div><div>5. The texture update fails in sqSqueakOSXMetaView.m:439.</div><div><br></div><div>Nothing of that is out of the ordinary. The tuple (displayBits, displayWidth, displayHeight) seems correct. This leaves the way we free the old texture and allocate a new one.</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 27.04.2022 11:58:31 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hi Lauren --<div><br></div><div>Nope. It just happened by chance. And only in a -f build. Hmm...</div><div><br></div><div>[</div><div> DisplayScreen setNewScreenSize: (1024@768) * 1.ยด</div><div> self currentWorld doOneCycle.</div><div> DisplayScreen setNewScreenSize: (1024@768) * 2.</div><div> self currentWorld doOneCycle.<br></div><div>] repeat.</div><div><br></div><div>Maybe it is a (Metal) texture allocating/freeing issue ...</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 27.04.2022 10:45:02 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hi Lauren --<div><br></div><div>Thanks for reporting this. I was able to reproduce the issue. I am looking into it right now.</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 27.04.2022 07:12:41 schrieb Lauren Pullen <drurowin@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">Hi List,
<br>
<br>What the subject line says. I had just toggled the UI scale between
<br>200% and 300% and back again and the window had shrunk, so I resized it
<br>to maximize it again and the VM aborted.
<br>
<br>The the last call from the VM was in
<br>-[sqSqueakOSXMetalView loadTexturesSubRectangle:]
<br>-[sqSqueakOSXMetalView drawRect:]
<br><br></div></blockquote>
</div></div></blockquote></div></div></blockquote></div></div></blockquote></div>