On 27 December 2010 23:49, Esteban Lorenzano <[email protected]> wrote: > Hi, > I'm having random crashes in a production image. This crashes occurs without > leaving any information available... it just crash. No PharoDebug.log, no > dump, nothing... finally, yesterday I get a PharoDebug.log (which I'm > attaching) with some error information... but frankly I don't know if this is > the reason the image is crashing or some other random error. > Some other elements I'm seeing is: > > - Seaside sessions are in fact never removed unless I manually execute > garbage collect. > - WeakArray FinalizationDependents is bigger than usual (90 instances), > elements are mostly WeakIdentityDictionary and MaWeakIdentityDictionary (most > of them empty but some other with sizes from 700 to 4000). > > I'm using a Pharo 1.1.1 with Seaside 3.0 and Magma 1.1r2 > The VM is any VM (exuperi 0.15f or unix cog) . > OS is "some kind of linux"... looks like a "custom suse". > Okay, you're using oscog.35 which predates new finalization.. at least it is not in a play.
> Well... and I'm completely lost. Any help will be very appreciated... even on > ways on how to get more info of my crashing system (redirecting standard and > error output does not works either)... And the access I have to the O.S. is > also limited. > well, all i can say that you should start digging from here: 'Error: highBit is not defined for negative integers' what if some error message prints numbers and using highbit for on negative one? it will then loop forever, recursively until there is a no free space left. but that of course could be anything else. > Cheers, > Esteban > > -- Best regards, Igor Stasenko AKA sig.
