<div dir="ltr">Hi Chris,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 22, 2014 at 11:54 AM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I try with the -memory parameter instead of -mmap, then Cog crashes<br>
immediately with -memory 2200m when launching the stock 4.5 image..<br></blockquote><div><br></div><div>Yes, that's your limit with X11. 32-bit linux reserves the top 1Gb for kernel space, leaving 3Gb for user processes. Once you factor in space taken for the VM and the X11 libraries (plus sundries) 2200mb is simply too much memory and the system crashes in X11 startup. So for the moment you'll need to peg things at 2100mb or 2000mb.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
On Thu, May 22, 2014 at 1:44 PM, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
> On Thu, May 22, 2014 at 1:00 PM, David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>> wrote:<br>
>> Usually on a unix system, a "No such file or directory" error means<br>
>> exactly what it says. A file named "/dev/dsp" is a device file in the /dev<br>
>> pseudo-file system, which presumably is not present. Various flavors of<br>
>> Linux or Unix might have different sound systems active, and might have<br>
>> different naming conventions for device files.<br>
>><br>
>> I can't think of any reason why this should have an interaction with<br>
>> object memory allocation. If it seems to be VM related, try running with<br>
>> an interpreter VM or a different version of Cog and see if the symptoms<br>
>> change.<br>
><br>
> It's because there's a System beep somewhere in there and I was just<br>
> interjecting the question-- why the heck do we have System beep(s)<br>
> embedded in the system?<br>
><br>
> But let's please not focus on that right now. I really want to ask<br>
> the more important question whether there's a problem with Cog.<br>
><br>
> None of the symptoms happen with the Interpreter VM (2357).<br>
><br>
> You can easily reproduce it yourself with Cog. Just start the base<br>
> Squeak4.5 image with the -mmap 2000m argument.<br>
><br>
> Then, in a workspace:<br>
><br>
> self halt.<br>
><br>
> Do It, then press Proceed on the debugger that appears.<br>
><br>
> Does the problem occur for you too? It's related to amount reclaimed<br>
> by the garbage-collector, but clearly we're not out of memory....<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>