Skip to content

Conversation

@agampa263
Copy link
Contributor

No description provided.

@CLAassistant
Copy link

CLAassistant commented Jul 16, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

❌ agampa263
❌ karuppaiyak
You have signed the CLA already but the status is still pending? Let us recheck it.

@rdkcmf-jenkins
Copy link
Contributor

Coverity Issue - Resource leak

Handle variable "sockfd" going out of scope leaks the handle.

High Impact, CWE-404
RESOURCE_LEAK

Issue location

This issue was discovered outside the diff for this Pull Request. You can find it at:
Tests/L1Tests/tests/test_ScreenCapture.cpp:211


std::string response = "HTTP/1.1 200 OK\r\nContent-Length: 0\r\n\r\n";
send(connection, response.c_str(), response.size(), 0);
ssize_t bytesSent = send(connection, response.c_str(), response.size(), 0);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coverity Issue - Resource leak

Handle variable "connection" going out of scope leaks the handle.

High Impact, CWE-404
RESOURCE_LEAK

EVENT_SUBSCRIBE(0, _T("uploadComplete"), _T("org.rdk.ScreenCapture"), message);
EVENT_SUBSCRIBE_1(0, _T("uploadComplete"), _T("org.rdk.ScreenCapture"), message);

EXPECT_EQ(Core::ERROR_NONE, handler.Invoke(connection, _T("uploadScreenCapture"), _T("{\"url\":\"http://127.0.0.1:11111\"}"), response));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coverity Issue - Resource leak

Handle variable "connection" going out of scope leaks the handle.

High Impact, CWE-404
RESOURCE_LEAK

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.

5 participants