Pharo image crash with Seaside App

Hi,

Version: Pharo 7.0
OS: Windows 8.

Which is the best way to get any error description when the Pharo image
crash ?

PharoDebug.log - does not have any information
stderr - does not have any information

Stoping the execution is not working ("Control" + "-")
https://stackoverflow.com/questions/24788115/if-my-pharo-image-goes-into-an-infinite-loop-how-do-i-break-out-of-the-loop

The problem is a "self call: WAMyComponent new".

ComponentA call ComponentB, then ComponentB call ComponentC, and last (here
is the problem) ComponentC call ComponentA again.

Is not an infinite loop because this cycle goes only one (well not even one
because the last call crash the image).

WASession allInstances size. "answer 6"
WACache allInstances size. "answer 0"

Maybe there is an issue in the call sequence with Seaside but this should
not crash the image.

Researching on this right now ...

regards,
bruno



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Hi,

It seems that the problem is fixed.

Not sure why Pharo image went freeze because it was a Seaside problem.
(maybe i should execute the same on GemStone/S to see the result).
Also not sure why Control + "-" did not halt the execution.
Even in one occasion make Windows 8 fail.

The problem was the reuse of already created components in as argument of
call.
editComponent := WAEditComponent new.
self call: editComponent.

This inst var was store in a parent and at some point instead of creating a
new component for the call we call again:
self call: editComponent.

After changing all call to a new fresh WAEditComponent the problem was
fixed. It seems that Seaside went into a infinite rendering loop (after all
:) because the already instantiated element.

Any thought about this is welcome because i did not totally close this issue
:)

regards,
bruno




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html