<div dir="ltr"><div><div><div><div>I traced this back to<br></div>Object&gt;&gt;withArgs:executeMethod:<br>(primitive 188)<br><br>in OpalCompiler&gt;&gt;#evaluate <br></div><br></div></div>It does not happen on squeaks spur vm as far as I know (but I don&#39;t know what is the latests squeak spur vm).<br><br><br><div><div><br><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-02-08 5:17 GMT+01:00 Martin Dias <span dir="ltr">&lt;<a href="mailto:tinchodias@gmail.com" target="_blank">tinchodias@gmail.com</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Very interesting...<div><br></div><div>I created <a href="https://pharo.fogbugz.com/f/cases/17543/VM-crash-in-Windows-when-compiling-many-symbols" target="_blank">case 17543</a>, with Vincent&#39;s script and other quotes from this thread. I did it because this Windows issue is independent from Epicea (whose integration only exposed the Windows issue).<span class=""><font color="#888888"><div><div><br></div><div>Martin<br></div></div></font></span></div></div><div class=""><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Feb 6, 2016 at 6:41 AM, Max Leske <span dir="ltr">&lt;<a href="mailto:maxleske@gmail.com" target="_blank">maxleske@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word">Changing the scheduler didn’t have any effect. However, it seems to me that the size of the input matters. I can make it work in two ways:<div>1. delete a line. If the line’s too short it won’t work though</div><div>2. delete a couple of characters from some symbols</div><div><br></div><div>That would suggest that not the number of symbols / items in the array is significant but the number of bytes. So maybe there’s a problem with memory allocation in the VM. I haven’t been able to come up with an exact number, but the VM starts crashing at around 7096 characters. Sometimes I can go over 7100, other times not. Smaller numbers always work.</div><div><br></div><div>HTH,</div><div>Max</div><div><div><div><br><div><blockquote type="cite"><div>On 06 Feb 2016, at 07:25, Ben Coman &lt;<a href="mailto:btc@openinworld.com" target="_blank">btc@openInWorld.com</a>&gt; wrote:</div><br><div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">On Sat, Feb 6, 2016 at 12:59 PM, Martin Dias &lt;</span><a href="mailto:tinchodias@gmail.com" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">tinchodias@gmail.com</a><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">&gt; wrote:</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">In fact, this integration step<br>(<a href="https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z" target="_blank">https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z</a>) was<br>already passed by Epicea in December. That was before spur, it might be<br>related to spur.<br><br>That time, the integration of Epicea revealed a bug in delay&#39;s scheduling...<br></blockquote><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Was that these issues integrated in build 50466...</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="https://pharo.fogbugz.com/default.asp?17066" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://pharo.fogbugz.com/default.asp?17066</a><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="https://pharo.fogbugz.com/default.asp?13756" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://pharo.fogbugz.com/default.asp?13756</a><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">which should have left the current scheduler as DelayExperimentalSpinScheduler</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">but in current build 50564 &quot;Delay delaySchedulerClass&quot; --&gt;</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">DelayMicrosecondScheduler</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Maybe Delay class &gt;&gt; initialize has been executed since</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">     Scheduler ifNotNil: [ Scheduler stopTimerEventLoop ].</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">     Scheduler := DelayMicrosecondScheduler new.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">     Scheduler startTimerEventLoop.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">     Smalltalk addToStartUpList: self.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">but I don&#39;t see any updates that might have invoked it.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Anyway, maybe changing that will help.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">cheers -ben</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">maybe now it&#39;s revealing some bug in Windows+spur...?<br><br>Martin<br><br><br>On Fri, Feb 5, 2016 at 10:09 AM, Blondeau Vincent<br>&lt;<a href="mailto:vincent.blondeau@worldline.com" target="_blank">vincent.blondeau@worldline.com</a>&gt; wrote:<br><blockquote type="cite"><br>If you remove any line, it stops crashing…<br><br>I really don’t know what is going on…<br><br><br><br>Vincent<br><br><br><br>De : Pharo-dev [<a href="mailto:pharo-dev-bounces@lists.pharo.org" target="_blank">mailto:pharo-dev-bounces@lists.pharo.org</a>] De la part de<br>Henrik Nergaard<br>Envoyé : vendredi 5 février 2016 14:03<br><br><br>À : Pharo Development List<br>Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN]<br>We are in &quot;code freeze&quot; for Pharo 5)<br><br><br><br>Removing<br><br>#(IRPrinterV2 #(visitStoreTemp: visitStoreRemoteTemp:<br>visitPopIntoLiteralVariable: visitPushTemp: visitReturnLiteral:<br>visitStoreInstVar: visitStoreLiteralVariable: visitPushLiteralVariable:<br>visitPushInstVar: visitJump: visitPushLiteral: label: visitPushArray:<br>visitPopIntoTemp: visitReturnInstVar: visitPopIntoRemoteTemp:<br>visitTempVector: visitJumpIf: visitPushRemoteTemp: visitPopIntoInstVar:<br>visitSend: ))<br><br>And it stops crashing.<br><br><br><br>- BTW, there is not crash.dmp, does it works with spur?<br><br><br><a href="https://pharo.fogbugz.com/f/cases/17506/when-an-Image-crashes-a-crash-dmp-file-is-created-but-nothing-is-written-to-it-Windows" target="_blank">https://pharo.fogbugz.com/f/cases/17506/when-an-Image-crashes-a-crash-dmp-file-is-created-but-nothing-is-written-to-it-Windows</a><br><br><br><br>Best regards,<br><br>Henrik<br><br><br><br>From: Pharo-dev [mailto:<a href="mailto:pharo-dev-bounces@lists.pharo.org" target="_blank">pharo-dev-bounces@lists.pharo.org</a>] On Behalf Of<br>Blondeau Vincent<br>Sent: Friday, February 5, 2016 1:54 PM<br>To: Pharo Development List &lt;<a href="mailto:pharo-dev@lists.pharo.org" target="_blank">pharo-dev@lists.pharo.org</a>&gt;<br>Subject: Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE:<br>[ANN] We are in &quot;code freeze&quot; for Pharo 5)<br><br><br><br>Very strange bug indeed that happens on windows machines that crashes the<br>VM. I succeeded to reduce the problem to an evaluation of a collection…<br><br>Can someone have the same issue under Windows or Mac?<br><br><br><br>To reproduce : Copy paste the contents of the attached file in the<br>playground and print it or do it<br><br>It works on pre-spur vm.<br><br><br><br>BTW, there is not crash.dmp, does it works with spur?<br><br>Vincent<br><br><br><br>De : Pharo-dev [mailto:<a href="mailto:pharo-dev-bounces@lists.pharo.org" target="_blank">pharo-dev-bounces@lists.pharo.org</a>] De la part de<br>Marcus Denker<br>Envoyé : vendredi 5 février 2016 13:01<br>À : Pharo Development List<br>Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN]<br>We are in &quot;code freeze&quot; for Pharo 5)<br><br><br><br><br><br>On 05 Feb 2016, at 12:40, Marcus Denker &lt;<a href="mailto:marcus.denker@inria.fr" target="_blank">marcus.denker@inria.fr</a>&gt; wrote:<br><br><br><br>I will try do integrate it now…<br><br><br><br><br><br><br><br>No, it still fails.<br><br><br><br><br><a href="https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=win/706/" target="_blank">https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/label=win/706/</a><br><br><br><br>The last test it executed seems to be this:<br><br>running suite: Refactoring-Tests-Environment<br><br>starting testcase: RBBrowserEnvironmentTest&gt;&gt;testAndEnvironment ...<br><br>Very strange...<br><br>      Marcus<br><br><br><br><br><br>________________________________<br><br><br>Ce message et les pièces jointes sont confidentiels et réservés à l&#39;usage<br>exclusif de ses destinataires. Il peut également être protégé par le secret<br>professionnel. Si vous recevez ce message par erreur, merci d&#39;en avertir<br>immédiatement l&#39;expéditeur et de le détruire. L&#39;intégrité du message ne<br>pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra<br>être recherchée quant au contenu de ce message. Bien que les meilleurs<br>efforts soient faits pour maintenir cette transmission exempte de tout<br>virus, l&#39;expéditeur ne donne aucune garantie à cet égard et sa<br>responsabilité ne saurait être recherchée pour tout dommage résultant d&#39;un<br>virus transmis.<br><br>This e-mail and the documents attached are confidential and intended<br>solely for the addressee; it may also be privileged. If you receive this<br>e-mail in error, please notify the sender immediately and destroy it. As its<br>integrity cannot be secured on the Internet, the Worldline liability cannot<br>be triggered for the message content. Although the sender endeavours to<br>maintain a computer virus-free network, the sender does not warrant that<br>this transmission is virus-free and will not be liable for any damages<br>resulting from any virus transmitted.<br><br><br>________________________________<br><br>Ce message et les pièces jointes sont confidentiels et réservés à l&#39;usage<br>exclusif de ses destinataires. Il peut également être protégé par le secret<br>professionnel. Si vous recevez ce message par erreur, merci d&#39;en avertir<br>immédiatement l&#39;expéditeur et de le détruire. L&#39;intégrité du message ne<br>pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra<br>être recherchée quant au contenu de ce message. Bien que les meilleurs<br>efforts soient faits pour maintenir cette transmission exempte de tout<br>virus, l&#39;expéditeur ne donne aucune garantie à cet égard et sa<br>responsabilité ne saurait être recherchée pour tout dommage résultant d&#39;un<br>virus transmis.<br><br>This e-mail and the documents attached are confidential and intended<br>solely for the addressee; it may also be privileged. If you receive this<br>e-mail in error, please notify the sender immediately and destroy it. As its<br>integrity cannot be secured on the Internet, the Worldline liability cannot<br>be triggered for the message content. Although the sender endeavours to<br>maintain a computer virus-free network, the sender does not warrant that<br>this transmission is virus-free and will not be liable for any damages<br>resulting from any virus transmitted.</blockquote></blockquote></div></blockquote></div><br></div></div></div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div></div></div></div></div>