Monday, December 19, 2011 10:31 AM
I've searched people who had the same error as me : "Not enough memory to complete requested operation".
The issues are : too big files or too many sources. In my case I have a MP3 file (1 hour length in low quality), and I transcode it to 12 '5 min' WMA files and on 16 streams 24/7.
For each encoding I create a new Encodere.Job object (1 object per MP3 file). After several hours I have the error "Not enough memory to complete requested operation". If I stop the program and relaunch it, the file on which I got the error was transcoded well and the process fails again after several hours on another MP3 file.
Do you have any idea why I have this problem ?
* .NET 4 / C# 4
* Windows 2008 R2 SP1 (with 2 processors and 8 GB)
* Binaries bluid in x86
Tuesday, December 20, 2011 4:31 PM
Are you doing this in encoder or in your own application based on the sdk? If you are using the sdk, then you need to add the 'Large Address Aware' flag to your project. That being said 16 streams is usually not recommended as it can be too much for some machines.
Wednesday, October 03, 2012 5:28 PM
I am experiencing exactly the same problem with a service that sequential transcodes large numbers of small wav files to wma using the SDK. The process works fine for several hours then fails with the "Not enough memory to complete requested operation" error. At this point the process memory usage is only about 130MB and the system has more than 4GB of RAM free so I can't see why this is happening. On restarting the service the file that cause the error is processed without any problems.
Are you suggesting that any application using the SDK should add the 'Large Address Aware' flag or should this only be relevant for applications that are using very large amounts of memory?