On 13.05.2009, at 17:40, Will Sheppard wrote:
After we replaced all the ‘cocoon:’ protocol calls with 'http://localhost/path/to/cocoon'
, the memory leak disappeared. No matter how many times or how fast
the pipeline was hit, memory usage would always come down just
before it reached 100Mb.
Thanks for sharing your observations. This might be related to a
problem we are currently facing.
The use of the cocoon: protocol has several other pros additional to
error stack:
- caching
- map:generate in caller and map:serialize in callee will be optimized
and the SAX stream is passed
We have a sitemap where a calls b, which calls c, which calls d (see below).
The reason it's set up like this is so we can view each stage on its own, to
facilitate development and debugging.
We were noticing massive memory leakage. If the a/*/* pipeline was hit 200
times, the memory usage would
