On Mon, Dec 22, 2014 at 12:04:16PM -0600, Chris Muller wrote:
On Sun, Dec 21, 2014 at 5:59 PM, David T. Lewis lewis@mail.msen.com wrote:
On Sun, Dec 21, 2014 at 10:06:20PM +0100, Levente Uzonyi wrote:
The problem was that an error occured, so Seaside was trying to send an email about it. But generating the stack trace for the email resulted in another error. This recursively triggered another attempt to create an email. The runaway process consumed 850MB of memory, and did not trigger the low space watcher, probably because it was a low priority (30) process (probably a Seaside request handler). Someone who's more familiar with Seaside should fix this issue. There may even be a patch for this in the official repository.
To fix the problem, I downloaded the image, terminated the runaway process, saved it as a new version, and uploaded it. Then I stopped the service, modified it to use the new image, and restarted it.
... snip ... I am downloading the big squeaksource.3 image and I'll look and see if I can spot anything more about the cause (but I am not a Seaside expert
Hi Dave, I encountered this problem with the squeaksource code October of 2013, when I was doing the Magma-backed source.squeak.org:
http://lists.squeakfoundation.org/pipermail/box-admins/2013-October/001544.h...
and fixed it in the versions at:
After that, you had saved squeaksource.com from oblivion, but did not (IIRC) incorporate the fixes and improvements I had made to the SS code in trunk. I _really think_ you should consider merging those versions into the version that runs SqueakSource.com -- as there are other fixes and improvements besidse this one.
Thanks Chris.
Good idea. I can't look at it now, but I'll see if I can do as you suggest next week.
Dave