Hi Tudor,<br><br><div class="gmail_quote">On Thu, Mar 15, 2012 at 2:55 PM, Tudor Girba <span dir="ltr"><<a href="mailto:tudor@tudorgirba.com">tudor@tudorgirba.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi,<br>
<br>
The problem is that I cannot get it for you because it's proprietary code, and the issue raised when loading the code from a Monticello repository.<br></blockquote><div><br></div><div>I sign non-disclosure agreements and destroy files once I'm done :) So if you can get it to crash loading from a package-cache and you're happy for me to sign an NDA I can still look at it. But only if you;re comfortable and only if you have a reproducible case.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I got some strange crashes in other contexts but without having time to dig into these :(. I will try to keep my eyes opened and find some reproducible case.<br>
<br>
Cheers,<br>
Doru<br></blockquote><div><br></div><div>cool.</div><div><br></div><div>cheers!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div class="h5"><br>
<br>
On 15 Mar 2012, at 20:03, Igor Stasenko wrote:<br>
<br>
><br>
> On 15 March 2012 19:28, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
>><br>
>><br>
>><br>
>> On Tue, Mar 13, 2012 at 7:44 AM, Tudor Girba <<a href="mailto:tudor@tudorgirba.com">tudor@tudorgirba.com</a>> wrote:<br>
>>><br>
>>> Strange. I tried to reproduce the problem, but following the same path<br>
>>> worked fine the second time.<br>
>><br>
>><br>
>> Such GC bugs are extremely sensitive to exactly the sequence of mutations in the heap. So the time in between mouse clicks or keyboard presses, or even the length of delays or the date and time can change the form of the heap. The only way I know to reproduce this kind of bug reliably is to write a doit that causes the system to crash without user intervention. You can either supply the doit in a file to the VM at startup or (more convenient for those debugging it) write a doit that starts with a snapshot, e.g.<br>
>><br>
>> Smalltalk saveAs.<br>
>> Crasher new crash<br>
>><br>
><br>
> Not again this flaky GC/become stuff. I was hoping that last one we<br>
> busted in summer..<br>
><br>
><br>
> --<br>
> Best regards,<br>
> Igor Stasenko.<br>
<br>
</div></div><font color="#888888">--<br>
<a href="http://www.tudorgirba.com" target="_blank">www.tudorgirba.com</a><br>
<br>
"No matter how many recipes we know, we still value a chef."<br>
<br>
<br>
<br>
<br>
<br>
<br>
</font></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div><br>