Uncleaned Resources After Failed App Start

[tandharia]

Describe the bug
When an app fails to start because of bad parameters (like invalid stack size), the module stays loaded in memory and its entry in the OS_module_table is not removed. Because of this, apps with the same name can't be started. And if multiple attempts are made to start apps with bad parameters, the OS_module_table can fill up with invalid entries, blocking new apps from starting. Since the app entries in CFE_ES_Global.AppTable are deactivated, CFE_ES_STOP_APP_CC can’t clean them up.

Expected behavior
If an app fails to start because of bad parameters, all resources associated with the app are cleaned up

System observed on:
OS: RHEL 8.10

Reporter Info
Tvisha Andharia - GSFC 582 intern