-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RDKB-59288 Overall Memory usage is increasing continuously #230
RDKB-59288 Overall Memory usage is increasing continuously #230
Conversation
Reason for change: Data is not freed which creates memory leak Test Procedure: Debug Priority: P0 Risks: Low Signed-off-by: Samyuktha Karthikeyan <samyuktha_karthikeyan@comcast.com>
Reason for change: To free the memory after allocation Test Procedure: Flash the build in HUB6 and check for increase in the memory Priority: P0 Risks: Low Signed-off-by: Samyuktha Karthikeyan <samyuktha_karthikeyan@comcast.com>
Reason for change: To free the memory after allocation Test Procedure: Flash the build in HUB6 and check for increase in the memory Priority: P0 Risks: Low Signed-off-by: Samyuktha Karthikeyan <samyuktha_karthikeyan@comcast.com>
Reason for change: To free the memory after allocation Test Procedure: Flash the build in HUB6 and check for increase in the memory Priority: P0 Risks: Low Signed-off-by: Samyuktha Karthikeyan <samyuktha_karthikeyan@comcast.com>
Reason for change: To free the memory after allocation Test Procedure: Flash the build in HUB6 and check for increase in the memory Priority: P0 Risks: Low Signed-off-by: Samyuktha Karthikeyan <samyuktha_karthikeyan@comcast.com>
Reason for change: To free the memory after allocation Test Procedure: Flash the build in HUB6 and check for increase in the memory Priority: P0 Risks: Low Signed-off-by: Samyuktha Karthikeyan <samyuktha_karthikeyan@comcast.com>
Reason for change: To free the memory after allocation Test Procedure: Flash the build in HUB6 and check for increase in the memory Priority: P0 Risks: Low Signed-off-by: Samyuktha Karthikeyan <samyuktha_karthikeyan@comcast.com>
source/apps/levl/wifi_levl.c
Outdated
@@ -810,6 +810,10 @@ void push_radio_temperature_request_to_monitor_queue(wifi_mon_stats_request_stat | |||
data->u.mon_stats_config.data_type = mon_stats_type_radio_temperature; | |||
data->u.mon_stats_config.args.radio_index = radio_index; | |||
push_event_to_monitor_queue(data, wifi_event_monitor_data_collection_config, &route); | |||
if (data != NULL) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can remove the if and keep only free(data);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed the comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please address the comment
Reason for change: To free the allocated memory after its usage Test Procedure: 1.Flash the build in the issue device 2.Make sure Levl is enabled 3.Check for Memory Leak Priority: P0 Risks: Low Signed-off-by: Samyuktha Karthikeyan samyuktha_karthikeyan@comcast.com
Reason for change: To free the allocated memory after its usage
Test Procedure:
Priority: P0
Risks: Low
Signed-off-by: Samyuktha Karthikeyan samyuktha_karthikeyan@comcast.com