<body><div id="__MailbirdStyleContent" style="font-size: 12pt;font-family: calibri;color: #000000">
Thank you for this bug report. :)<div><br></div><div>The current clean-up strategy is to dismiss existing instances of UserInterfaceTheme. In your example, the current theme was not touched and is still active. That is, your environment as an active theme that is not in the list "UserInterfaceTheme allThemes". The release building process usually picks a new theme after the clean-up, which your example did not.</div><div><br></div><div>Anyway, I will fix the test to also consider the currently active theme. ;-)</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;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 18.09.2017 11:23:18 schrieb Stéphane Rollandin <lecteur@zogotounga.net>:</p>> UserInterfaceTheme cleanUp: true.<br>> <br>> or<br>> <br>> Smalltalk cleanUp: true.<br><br><br>Hmm I did:<br><br>100 timesRepeat: [Morph new userInterfaceTheme yourself].<br>UserInterfaceTheme cleanUp: true.<br>Smalltalk cleanUp: true.<br>UserInterfaceTheme current explore<br><br>... the scope stack was still populated.<br><br><br>Stef<br><br>
</blockquote>
</div></body>