Is there some shared memory space?
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 - 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
On 07.03.2014, at 11:55, roberto.minelli@usi.ch 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?
- 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
On Mar 7, 2014, at 12:24 PM, Max Leske <maxleske@gmail.com> wrote:
On 07.03.2014, at 11:55, roberto.minelli@usi.ch 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
Anyone on this? It is very frustrating for me. Cheers, Roby On Mar 7, 2014, at 1:05 PM, roberto.minelli@usi.ch wrote:
On Mar 7, 2014, at 12:24 PM, Max Leske <maxleske@gmail.com> wrote:
On 07.03.2014, at 11:55, roberto.minelli@usi.ch 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
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 BTW, are you on windows, linux, mac? which vm/image? Guille On Sat, Mar 8, 2014 at 2:55 PM, roberto.minelli@usi.ch < roberto.minelli@usi.ch> wrote:
Anyone on this? It is very frustrating for me.
Cheers, Roby
On Mar 7, 2014, at 1:05 PM, roberto.minelli@usi.ch wrote:
On Mar 7, 2014, at 12:24 PM, Max Leske <maxleske@gmail.com> wrote:
On 07.03.2014, at 11:55, roberto.minelli@usi.ch 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
On 08.03.2014, at 15:03, Guillermo Polito <guillermopolito@gmail.com> 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
BTW, are you on windows, linux, mac? which vm/image?
Guille
On Sat, Mar 8, 2014 at 2:55 PM, roberto.minelli@usi.ch <roberto.minelli@usi.ch> wrote: Anyone on this? It is very frustrating for me.
Cheers, Roby
On Mar 7, 2014, at 1:05 PM, roberto.minelli@usi.ch wrote:
On Mar 7, 2014, at 12:24 PM, Max Leske <maxleske@gmail.com> wrote:
On 07.03.2014, at 11:55, roberto.minelli@usi.ch 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
On 08.03.2014, at 23:12, btc@openInWorld.com wrote:
Max Leske wrote:
On 08.03.2014, at 15:03, Guillermo Polito <guillermopolito@gmail.com> 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, roberto.minelli@usi.ch <roberto.minelli@usi.ch> wrote: Anyone on this? It is very frustrating for me.
Cheers, Roby
On Mar 7, 2014, at 1:05 PM, roberto.minelli@usi.ch wrote:
On Mar 7, 2014, at 12:24 PM, Max Leske <maxleske@gmail.com> wrote:
On 07.03.2014, at 11:55, roberto.minelli@usi.ch 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
Solve. Neither image nor VM nor Fuel luckily :) Cheers, Max On 08.03.2014, at 23:15, Max Leske <maxleske@gmail.com> wrote:
On 08.03.2014, at 23:12, btc@openInWorld.com wrote:
Max Leske wrote:
On 08.03.2014, at 15:03, Guillermo Polito <guillermopolito@gmail.com> 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, roberto.minelli@usi.ch <roberto.minelli@usi.ch> wrote: Anyone on this? It is very frustrating for me.
Cheers, Roby
On Mar 7, 2014, at 1:05 PM, roberto.minelli@usi.ch wrote:
On Mar 7, 2014, at 12:24 PM, Max Leske <maxleske@gmail.com> wrote:
On 07.03.2014, at 11:55, roberto.minelli@usi.ch 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
Can you share what happened so we can avoid it? :D On Sun, Mar 9, 2014 at 9:02 PM, Max Leske <maxleske@gmail.com> wrote:
Solve. Neither image nor VM nor Fuel luckily :)
Cheers, Max
On 08.03.2014, at 23:15, Max Leske <maxleske@gmail.com> wrote:
On 08.03.2014, at 23:12, btc@openInWorld.com wrote:
Max Leske wrote:
On 08.03.2014, at 15:03, Guillermo Polito <guillermopolito@gmail.com> 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, roberto.minelli@usi.ch < roberto.minelli@usi.ch> wrote:
Anyone on this? It is very frustrating for me.
Cheers, Roby
On Mar 7, 2014, at 1:05 PM, roberto.minelli@usi.ch wrote:
On Mar 7, 2014, at 12:24 PM, Max Leske <maxleske@gmail.com> wrote:
On 07.03.2014, at 11:55, roberto.minelli@usi.ch 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
Well⦠donât delete those two lines when commenting out the version check :) verifyVersionFrom: aDecoder | streamVersion | <---------------------- streamVersion := aDecoder nextEncodedUint16. <------------------- (self version = streamVersion) ifFalse: [ FLBadVersion signalCurrentVersion: self version streamVersion: streamVersion ] On 10.03.2014, at 15:05, Guillermo Polito <guillermopolito@gmail.com> wrote:
Can you share what happened so we can avoid it? :D
On Sun, Mar 9, 2014 at 9:02 PM, Max Leske <maxleske@gmail.com> wrote: Solve. Neither image nor VM nor Fuel luckily :)
Cheers, Max
On 08.03.2014, at 23:15, Max Leske <maxleske@gmail.com> wrote:
On 08.03.2014, at 23:12, btc@openInWorld.com wrote:
Max Leske wrote:
On 08.03.2014, at 15:03, Guillermo Polito <guillermopolito@gmail.com> 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, roberto.minelli@usi.ch <roberto.minelli@usi.ch> wrote: Anyone on this? It is very frustrating for me.
Cheers, Roby
On Mar 7, 2014, at 1:05 PM, roberto.minelli@usi.ch wrote:
On Mar 7, 2014, at 12:24 PM, Max Leske <maxleske@gmail.com> wrote:
On 07.03.2014, at 11:55, roberto.minelli@usi.ch 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
participants (4)
-
btc＠openinworld.com -
Guillermo Polito -
Max Leske -
roberto.minelli＠usi.ch