Mythtranscode memory leak on cut+compress

[Martin van Es <martin@…>]

Lossy transcoding of DVB-C MPEG2 recording with cutmarks makes mythtranscode process leak memory untill the OOM killer kills the process and often mythfrontend before it ends, leaving the job unfinished and in error state. If however I transcode the cuts lossless first and then transcode the cutless recording to mp4 (same mp4 profile), there is a slight increase in memory consumption, but the transcode succeeds and all ends well.

[Stuart Auchterlonie]

Closing out old tickets.