-
-
Notifications
You must be signed in to change notification settings - Fork 791
[IOS] Memory leaks during argument parsing #17
Comments
A detailed analysis proves that successful command execution does not create new leaks, only commands returning a non-zero return value create leaks. The good thing is most of them are small in size, around 16 - 80 bytes per execution. Additionally, most of them occur inside A solution is planned in middle-term. The following screenshot is captured for IOS during command execution tests. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Argument parsing methods leaks memory. The following trace belongs to one of the leaks.
The actual cause is reusable nature of internal variables. FFmpeg executable does not perform a full cleanup on abnormal termination and exits without freeing some dynamic parts. But MobileFFmpeg does not call FFmpeg executable and some dynamic blocks remain unfreed.
A common solution is needed for both Android and IOS.
This issue was detected in
v2.0
but it looks like all versions are affected from this.The text was updated successfully, but these errors were encountered: