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] TypeError: Cannot read property 'clone' of null in SDPManagerUnified #154

Open
tiepviet opened this issue May 19, 2020 · 5 comments
Open

Comments

@tiepviet
Copy link
Contributor

/app/node_modules/medooze-media-server/lib/SDPManagerUnified.js:166
					mediaInfo = this.localInfo.getMedia(transceiver.media).clone();
					                                                      ^

TypeError: Cannot read property 'clone' of null
    at SDPManagerUnified.createLocalDescription (/app/node_modules/medooze-media-server/lib/SDPManagerUnified.js:166:60)
    at EventEmitter.Participant.sdpManager.on (/app/dist/lib/participant.js:117:62)
    at EventEmitter.emit (events.js:198:13)
    at EventEmitter.emit (domain.js:448:20)
    at Timeout.setTimeout [as _onTimeout] (/app/node_modules/medooze-media-server/lib/SDPManagerUnified.js:240:18)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
error Command failed with exit code 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
@murillo128
Copy link
Member

could you paste a dump of the localInfo object and the capabilities info? also, could you explain how are you are doing the sdp O/A?

@tiepviet
Copy link
Contributor Author

Sorry for my problem. I couldn't reproduce this bug. So, I will close it.

@murillo128
Copy link
Member

If you happen to reproduce it, please feel free to re-open it.

@skmax
Copy link
Contributor

skmax commented May 26, 2020

@murillo128 Also experience the same error from time to time. Unfortunately, I could find out exact reproducing steps as well.

@tiepviet tiepviet reopened this Jun 22, 2021
@tiepviet
Copy link
Contributor Author

Recently this error appears frequently on our server. So, I will reopen this issue.

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

No branches or pull requests

3 participants