Have you managed to recreate the memory leak using the PARSE inside a loop or was that an educated assumption?
I'm not a service engineer, I'm a developer. It takes something fairly seismic to make me actually try things out - so you can safely assume that it's the latter.
Quote:
Any plans to address this issue in the future?
Well, strictly speaking this is a documented behaviour, not a defect, not a memory leak. If you create 10,000 parsers in a loop within a flow, the flow will not deallocate those parsers until the end of the flow ( just in case you might have wanted to reuse them ). So it ends up looking very much like a leak, but in fact all the memory will eventually be reclaimed ( assuming that the EG is still around to reclaim it ).
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum