Solve. Neither image nor VM nor Fuel luckily :) Cheers, Max
On 08.03.2014, at 23:15, Max Leske <[email protected]> wrote: > > On 08.03.2014, at 23:12, [email protected] wrote: > >> Max Leske wrote: >>> >>> >>> On 08.03.2014, at 15:03, Guillermo Polito <[email protected]> wrote: >>> >>>> Hmm, as far as I know there is no "shared memory space"... or bah.. what >>>> do you mean by that? >>>> >>>> From my understanding I'd say that when you do: >>>> >>>> "- I fix the bug (i.e., commenting the self error)" >>>> >>>> you introduce some side effect that causes an infinite recursion => lots >>>> of contexts are reified because the vm stack gets full => you run out of >>>> memory >>> >>> No, it seems that the error lies with Fuel, although I can’t yet say why. >>> I’m still investigating. >>> >>> Max >> >> Max, You've been able to reproduce the problem? > > Not really. I’m working on it with Roberto and post back once we’ve figured > out more. I’m pretty sure though that VM and image are fine (apart from > limiting the heap size to 500MB *grml*). > > >> >>> >>>> >>>> BTW, are you on windows, linux, mac? which vm/image? >>>> >>>> Guille >>>> >>>> >>>> On Sat, Mar 8, 2014 at 2:55 PM, [email protected] >>>> <[email protected]> wrote: >>>> Anyone on this? It is very frustrating for me. >>>> >>>> Cheers, >>>> Roby >>>> >>>> On Mar 7, 2014, at 1:05 PM, [email protected] wrote: >>>> >>>> > >>>> > On Mar 7, 2014, at 12:24 PM, Max Leske <[email protected]> wrote: >>>> > >>>> >> >>>> >> On 07.03.2014, at 11:55, [email protected] wrote: >>>> >> >>>> >>> Hi guys, >>>> >>> >>>> >>> I am experiencing a very strange problem that makes me think there is >>>> >>> some shared memory problem with Pharo. >>>> >>> >>>> >>> Here are the steps that lead to the problem: >>>> >>> - I have an image, I do something (i.e., materializing objects with >>>> >>> Fuel) >>>> >>> - I encounter a problem and a debugger pops up with a “self error: >>>> >>> something" >>>> >>> - I close the debugger >>>> >>> - I close the image >>>> >> >>>> >> Do you save the image? If so, are you saving references to the already >>>> >> materialized objects? >>>> > >>>> > Of course, I did not save the image. Otherwise I’d have understood the >>>> > behavior. >>>> > >>>> >> >>>> >>> - I reopen the image >>>> >>> - I fix the bug (i.e., commenting the self error) >>>> >>> - I re-run the same thing as in the first step >>>> >>> - An OutOfMemory error appears. >>>> >>> >>>> >>> Any clue? >>>> >>> >>>> >>> Thanks, >>>> >>> Roberto
