Thanks for the additional information. The amount of memory seems to be quite enough ;-). Although the issue is no longer occuring in the upcoming release, we need to look further into what's causing this problem for version 4.2.3. Apparently it is not (directly) related to some memory leak.