When relying on RealtimeCorpusController the service let the tomcat crash for multiple mediaunti documents
When the document contains multiple media unit (5 or more), their is a big issue when the gapp in use relies on RealtimeCorpusController class instead of the standard SerialAnalyserCorupusController.
We encounter a huge memory leak even in the case of very small text document.
One easy solution is to change the behavior of the service, not to create a single corpus with every text unit as document inside but to create a corpus with a single document per media unit.