ooh, sounds like a tough one!
you might try turning on debugging and logDebuggerStackToFile in the
image to see if you get any (squeak) stack traces related to this.
is there any stack backtrace ("where") available when you use gdb?
are you running WinterLong?
what is your disk space like on the partition where the logs are
written? (i was getting daily crashes a while back and it turned out
my logs were filling up the partition)
[scratches his head]
hal
On Jan 27, 2008, at 6:38 AM, sa9k063 wrote:
> Hello,
>
> I have a problem with our swiki I cannot figure out.
> After years without problems our swiki regularly crashes every
> other day
> or even just hours after being started.
> I located the most recently changed swikis and turned individual
> logging
> on, but haven't found anything unusual afaik. (still have the logs if
> necessary)
>
> I ran it in gdb then and it seems that it tries to allocate _way_ too
> much memory and thus is killed by the OS. it crashes on both boxes i
> tried, under two different OSes, happily chewing 512MB RAM and
> 1.5GB swap.
>
> unfortunately the debugger is killed, too:
>
> Program received signal SIGKILL, Killed.
> 0x080638c2 in allocateheaderSizeh1h2h3doFillwith ()
> (gdb) [1]+ Hangup: 1 squeak -headless
> Killed: 9
>
> a lot of these kernel messages appear:
>
> swap_pager_getswapspace(10): failed
>
> and finally,
>
> pid 8214 (gdb), uid xxx, was killed: out of swap space
>
>
> Any ideas how to dig further to have it running nicely like earlier
> on ?
>
>
> tia,
> t
>
> _______________________________________________
> Pws mailing list
> Pws@cc.gatech.edu
> https://mailman.cc.gatech.edu/mailman/listinfo/pws
>
_______________________________________________
Pws mailing list
Pws@cc.gatech.edu
https://mailman.cc.gatech.edu/mailman/listinfo/pws
