Hi Anonymous Developer,
In the past we were able to run a similar script for more than 7 days, adding more instances of the scaler to the pipeline causes the problem to appear faster. With just one instance of the scaler it fails just in the board that we have running at 400MHz but we are not sure if the speed is the reason of the failure in that board yet.
Now, you should be able to reproduce the same behavior of gst-launch in your application, this means that your application is likely not freeing the resources properly. gst-launch is the one that frees the memory and the resources in the scrip, it is not just the operating system, this means that you need to check what is wrong in the application in order to get the same results that gst-launch.
a) While using your application, could you run sys_top and check that the resources in the M3 are freed after each video iteration? Please check if the amount of used memory increments after every iteration.
b) In your application, are you destroying all or just part of the pipeline?
-David
- I just saw that you had attached the .cpp, I will take a look on it