We have confirmed that short-term repetition of the create_SWX and destroy_SWX functions of SWX610 causes a memory leak in the upper application (calling application).
Please implement the functions in such a way that the number of times they are executed is reduced.
- Recommended processing
1. create_SWX should be executed once in the initial process such as at application startup/form open.
2. Command processing such as epr, loop processing, etc:
3. Execute ”destroy_SWX” once in the termination process such as when the application is terminated/form is closed.
- Patterns of memory leak
Create_SWX and destroy_SWX are repeated for each command processing.
create_SWX/com_check_SWX
+ select_module_SWX, etc. + loop of END_status_SWX
+ destroy_SWX
create_SWX/com_check_SWX
+ START_epr_SWX, etc. + loop of END_status_SWX
+ destroy_SWX
As shown above, if create_SWX and destroy_SWX are repeated frequently for each command processing,
the TCP port release on the Windows OS side cannot keep up and memory leaks occur.
It is necessary to reduce the number of times create_SWX and destroy_SWX are executed as much as possible (using the aforementioned start/end-only method) or terminate the application periodically.
Please implement the functions in such a way that the number of times they are executed is reduced.
- Recommended processing
1. create_SWX should be executed once in the initial process such as at application startup/form open.
2. Command processing such as epr, loop processing, etc:
3. Execute ”destroy_SWX” once in the termination process such as when the application is terminated/form is closed.
- Patterns of memory leak
Create_SWX and destroy_SWX are repeated for each command processing.
create_SWX/com_check_SWX
+ select_module_SWX, etc. + loop of END_status_SWX
+ destroy_SWX
create_SWX/com_check_SWX
+ START_epr_SWX, etc. + loop of END_status_SWX
+ destroy_SWX
As shown above, if create_SWX and destroy_SWX are repeated frequently for each command processing,
the TCP port release on the Windows OS side cannot keep up and memory leaks occur.
It is necessary to reduce the number of times create_SWX and destroy_SWX are executed as much as possible (using the aforementioned start/end-only method) or terminate the application periodically.