Closed Bug 814969 Opened 13 years ago Closed 12 years ago

Datachannel demo stopped working due to expired STUN timers

Categories

(Core :: WebRTC: Networking, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: jesup, Assigned: jesup)

Details

(Whiteboard: [WebRTC] [blocking-webrtc-])

Attachments

(3 files)

Recently (not sure when) DataChannel tests on my Fedora17 machine stopped working (haven't tried others yet). In the logs I see failed mtransport streams, and a callstack shows it was a STUN timeout. Note that I have a lot of "audio" devices (thanks linux) that can't actually be opened and cause a delay in getUserMedia. 478148352[7f6b2c267bf0]: stream_failed called 478148352[7f6b2c267bf0]: NrIceCtx(PC:): state 3->5 478148352[7f6b2c267bf0]: Flow[5bbcd235109419a7:1,rtp(none)]; Layer[ice]: state 1->5 478148352[7f6b2c267bf0]: Flow[5bbcd235109419a7:1,rtp(none)]; Layer[dtls]: Lower lower experienced an error 478148352[7f6b2c267bf0]: Flow[5bbcd235109419a7:1,rtp(none)]; Layer[dtls]: state 1->5 478148352[7f6b2c267bf0]: WARNING: MediaPipeline Transport failed. This is not properly cleaned up yet: file ../../../../../media/webrtc/signaling/src/mediapipeline/MediaPipeline.cpp, line 245 WARNING: MediaPipeline Transport failed. This is not properly cleaned up yet: file ../../../../../media/webrtc/signaling/src/mediapipeline/MediaPipeline.cpp, line 245 478148352[7f6b2c267bf0]: Flow[5bbcd235109419a7:1,rtcp(none)]; Layer[ice]: state 1->5 478148352[7f6b2c267bf0]: Flow[5bbcd235109419a7:1,rtcp(none)]; Layer[dtls]: Lower lower experienced an error 478148352[7f6b2c267bf0]: Flow[5bbcd235109419a7:1,rtcp(none)]; Layer[dtls]: state 1->5 478148352[7f6b2c267bf0]: WARNING: MediaPipeline Transport failed. This is not properly cleaned up yet: file ../../../../../media/webrtc/signaling/src/mediapipeline/MediaPipeline.cpp, line 245 WARNING: MediaPipeline Transport failed. This is not properly cleaned up yet: file ../../../../../media/webrtc/signaling/src/mediapipeline/MediaPipeline.cpp, line 245 ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused
Looks like around 3-4 seconds from the previous ICE log to the failure
non-blocking - I think this is likely linux-only and only for specific configs where pulse errors out for seconds scanning the devices.
Assignee: nobody → rjesup
Whiteboard: [WebRTC] [blocking-webrtc+] → [WebRTC] [blocking-webrtc-]
no longer relevant.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: