On 25 Apr 2019, at 15:27, Esteban Maringolo <emaringolo@gmail.com> wrote:
Hi Sven,
On Thu, Apr 25, 2019 at 10:04 AM Sven Van Caekenberghe <sven@stfx.eu> wrote:
This way, you should run out of heap before the stack gets too large, since you allocate and hold on to an array in each frame.
I don't understand the purpose of such expression, since I'm not writing recursive code, where I pay special attention or save the image before running it, but I'm trying to find a way around accidental deep recursions.
I know, it was an experiment.
However I ran these examples in Dolphin and Pharo 7, and in Dolphin it triggers an memory exhaustion exception right away, and in Pharo it grows in memory use, slower than with the previous example, but with the same behavior (unresponsive image once the memory fills the available OS memory).
Too bad, this is a VM issue anyway.
Regards,
Esteban A. Maringolo