Skip to content

Conversation

@owen-lu-sercomm
Copy link

@owen-lu-sercomm owen-lu-sercomm commented Jan 30, 2026

Reason for change:
By scanning the code with Coverity, we identified a risk of memory leak in the WanManager, so added fix to avoid the memory leak.
Test Procedure:

  1. scanning the code with Coverity, to check if the memory leak is still reported
  2. plug in the wan cable and let wan up, check if the wan basic can work normally

Risks: Low

Reason for change:
By scanning the code with Coverity, we identified a risk of memory leak in the WanManager, so added fix to avoid the memory leak.
Test Procedure:
1. scanning the code with Coverity, to check if the memory leak is still reported
2. plug in the wan cable and let wan up, check if the wan basic can work normally
Risks: Low

Signed-off-by: Owen Lu <owen_lu@sercomm.com>
@owen-lu-sercomm owen-lu-sercomm requested a review from a team as a code owner January 30, 2026 10:31
@pradeeptakdas pradeeptakdas changed the title RDKBDEV-3364:Fix memory leak found by coverity in WanManager RDKCOM-5511: RDKBDEV-3364 Fix memory leak found by coverity in WanManager Jan 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant