-
Notifications
You must be signed in to change notification settings - Fork 127
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
Error Thunder: free(): invalid pointer #1720
Comments
Is this happening in R4 or in R5? We patched R4.4.2 forsveral edge cases where, during closing down, a dangling reference cuased segmentation fault crashed. 4.4.3 and onwards should have resolved these crashes.. |
Still seen in R5. I believe the issue might be related to plugins running as outofprocess true / Mode: local, but this is just our current theory. |
We have enabled debug build for wpeframework and we see this trace in crash case:
Seems to crash during deactivation of OCDM plugin, but is there anything else interesting from this log? |
Hi,
The WPEFramework::Core::Event::Lock() is pointing to code: https://github.com/rdkcentral/Thunder/blob/master/Source/core/Sync.cpp#L867 When searching online it seems crashes can be seen in rare cases when using pthread_cond_wait in certain cases. And the crash we are experiencing similarly happens rarely. Any help is appreciated! |
I think the first crash report is very helpfull. The mentioning of: During our QA cycles we focused more on the non-happu day scenarios. What if the connection breaks before the whole package is send, I guess your case, we need to be resiliant in those cases as well hence why these asserts have now been turned into if's. See master. So I guess, as you are probably working on R2, and I strongly encourage you to upgrade to R5 ;-) you need to backport some of those fixes. In R5 the ASSERT you have in your BT, does not exist anymore, because the Invoke now checks, before continuing, if the package received is complete and if not, it does not even process it because the link is broken, A COMRPC error is returned (one of the reasons why we introduced Core::hresult ;-) ) So I think we might be facing a different issue in R5, than in R2. In R2, the callstacks given above with the assert, make sure that the package is checked (w.r.t. size) before continue processing and do not ASSERT if it is a partial package. If you can make Callstacks with this issue for R5, Happy to guide you further to a solution.. |
Thanks for your response, your help with this is very valuable! I have tested on R5 and generated crash logs using wpeframework debug build type.
Any insight? Thanks again! |
Hi, just looking for any guidance on an error we encounter very rarely.
Does anyone know anything about this error log:
Thunder[3221]: *** Error in '/applications/wpebrowser/usr/bin/Thunder': free(): invalid pointer: 0x0000007f740dc618 ***
The error occurs after we activate and deactivate the Thunder plugins we are using many times e.g. > 10000 times.
In this case it seems to have happened around the time DisplayInfo plugin is being deactivated. And the error leads to a segmentation fault in Thunder causing the framework to crash entirely:
Thunder[3221]: Thunder shutting down due to a segmentation fault. All relevant data dumped
Any help or information at all is very much appreciated as this is a very difficult issue to debug.
Thanks.
The text was updated successfully, but these errors were encountered: