Hi Igor. I think I have a similar/same problem. I tried what you suggested about changing interpreterAllocationReserveBytes<br><br>I think it now doesn't crash because of that (I think), but the message <br><br>mprotect(x,y,PROT_READ | PROT_WRITE | PROT_EXEC): <span class="il">Cannot</span>
<span class="il">allocate</span> <span class="il">memory</span><br>
mprotect(x,y,PROT_READ | PROT_WRITE): Invalid argument<br><br>is still present. As far as I understood you said your crash was not due to that...but anyway, is that really a problem? is it fixed somewhere?<br>because I am having weird crashes and I cannot discover why.<br>
<br>thanks<br><br>mariano<br><br><div class="gmail_quote">2010/12/6 Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
OK, i changed<br>
<br>
interpreterAllocationReserveBytes<br>
| availableBytesPerPage maxFramesPerPage |<br>
availableBytesPerPage := self stackPageByteSize - self<br>
stackLimitOffset - self stackPageHeadroom.<br>
maxFramesPerPage := availableBytesPerPage / BytesPerWord // MFrameSlots.<br>
^2 raisedTo: (maxFramesPerPage * LargeContextSize * numStackPages) highBit<br>
<br>
to:<br>
<br>
interpreterAllocationReserveBytes<br>
| availableBytesPerPage maxFramesPerPage |<br>
availableBytesPerPage := self stackPageByteSize - self<br>
stackLimitOffset - self stackPageHeadroom.<br>
maxFramesPerPage := availableBytesPerPage / BytesPerWord // MFrameSlots.<br>
^2 << ((maxFramesPerPage * LargeContextSize * numStackPages) highBit -1)<br>
<br>
<br>
which is equal, except that latter its not using pow() function and<br>
somehow this no longer crashing the VM.<br>
The only conclusion i can make that this is really have nothing to do<br>
with mprotect() and other mmap() stuff.<br>
<br>
I can only guess, that xcode doing some aggressive optimization,<br>
violating calling conventions, or in some other way the fullGC is<br>
optimized in a way<br>
that it expected to be called from certain places (but obviously not<br>
from native code generated on the fly).<br>
<br>
That's really weird.<br>
<div><div></div><div class="h5"><br>
--<br>
Best regards,<br>
Igor Stasenko AKA sig.<br>
</div></div></blockquote></div><br>