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

[BUG]Device crashed due to destroyed resources ahead #1266

Closed
August88618 opened this issue Sep 9, 2021 · 3 comments · Fixed by #1277
Closed

[BUG]Device crashed due to destroyed resources ahead #1266

August88618 opened this issue Sep 9, 2021 · 3 comments · Fixed by #1277

Comments

@August88618
Copy link

Thread exited timeout,device crashed due to destroyed resources ahead

Function call process:freePeerConnection ->freeIceAgent ->freeConnectionListener
Key log:
log.txt

webrtc_crash.log

@August88618 August88618 added the bug Something isn't working label Sep 9, 2021
@disa6302
Copy link
Contributor

@August88618 ,

There is not enough information here. Can we get a stack trace or more info on when it is observed?

@August88618
Copy link
Author

@disa6302
Here is dump stack trace:
#0 0xb6b458c0 in pthread_mutex_lock ()
from /opt/arm-linux-gnueabihf-gcc4.9.4-uclibc1.0.31/arm-buildroot-linux-uclibcgnueabihf/sysroot/lib//libc.so.0
#1 0x002024ba in defaultLockMutex ()
#2 0xb6e4a1ac in connectionListenerReceiveDataRoutine () from /home/33588/upload/AWS/HBProject/Libs/app/libkvsWebrtcClient.so
#3 0xb6b47c5a in start_thread ()
from /opt/arm-linux-gnueabihf-gcc4.9.4-uclibc1.0.31/arm-buildroot-linux-uclibcgnueabihf/sysroot/lib//libc.so.0
#4 0xb6b0adea in clone ()
from /opt/arm-linux-gnueabihf-gcc4.9.4-uclibc1.0.31/arm-buildroot-linux-uclibcgnueabihf/sysroot/lib//libc.so.0
Backtrace stopped: previous frame identical to this frame

@disa6302 disa6302 added pending-research and removed bug Something isn't working labels Sep 13, 2021
@hassanctech hassanctech linked a pull request Sep 23, 2021 that will close this issue
@disa6302
Copy link
Contributor

Closing since the changes have been merged. @August88618 , please feel free to reopen or open a new issue if the issue is not resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants