Steps to reproduce:
1. Ingest a screen recording of 2-3 hours containing lots of slides (>240) which will create this number of player-slides with a "standard" workflow
2. Wait for the processing to come to the operation "distribute-downloads"
(Tested with 5.5GB media.zip (->Camera.mpg,Screen.mpg,Audio.mp2); 4 Cores, 6GB Memory, 3GB JavaHeap)
The distribution stops suddenly, Java is at 100%
The memory consumption not to suddenly peak (is this related to the jetty "memory leak" error?)
The distribution to be finished.
Workaround (if any):
Increasing Java Heap Space on startup seems to help a bit (this will catch some of the peaks before they become critical).
Decrease the number of player-slides detected with the videosegmenter configuration options (was not successful with that)