I'm not sure what you mean by "same behavior".  If I modify TEST in exec107
to do 

   set_max_mem (50_000_000)

it still passes - actually, it fails but only because of the messages

   Cannot allocate memory: too much in comparison with maximum allowed!

which have now been removed.  So adding `set_max_mem' causes test to behave
identically for me.

I should also emphasize that execution of the test case in the original
report does *not* (apparently) cause an infinite loop.  But it takes *much*
longer than expected before an "out of memory" exception is raised.