Skip to content
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

Smartlink crash fix #1819

Merged

Conversation

Karthick-Somasundaresan
Copy link
Contributor

No description provided.

@Karthick-Somasundaresan Karthick-Somasundaresan marked this pull request as draft January 6, 2025 09:47
@@ -1174,6 +1225,21 @@ namespace Thunder {
class Connection : public LinkType<INTERFACE> {
private:
using Base = LinkType<INTERFACE>;
class EventSubscriber: public Core::Thread {
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we really need a thread here ? This will always (per connection) require an 8MB callstack. I thnk you can "reuse" the ResouceMonitor Thread (communication thread) as this is probably just to request a registration ? Or if we need a thread, could we do something to limit it to 1 thread for all Conenction types per process ?

uint32_t retVal = Core::ERROR_UNAVAILABLE;
Core::JSONRPC::Message response;
const string parameters("{ \"event\": \"" + eventName + "\", \"id\": \"" + Base::Namespace() + "\"}");
auto result = Base::template Invoke<string>(DefaultWaitTime, "register", parameters, response);
Copy link
Contributor

Choose a reason for hiding this comment

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

Oke, synchronous Invoke, so communication thread is not an option :-) Maybe than 1 thread for all processes that have this ?

@pwielders pwielders merged commit 47f5bb4 into rdkcentral:master Jan 21, 2025
74 of 75 checks passed
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.

2 participants