Subscriber Scheduler: fix memory leak that may occur on failure during start
Description
When calling SOPC_SubScheduler_Start
and in case of failure during initialization (e.g.: no MQTT broker available), a memory leak was possible even if SOPC_SubScheduler_Stop
was called afterwards.
Analysis
This was due to bad management of 2 result statuses values in init_sub_scheduler_ctx
(1 boolean and 1 status).
Avoid to use 2 different variables for result status which leads to forget updating both at each step.