WebRTC Assertion failure: mIceState != kIceGathering, at media/webrtc/signaling/src/peerconnection/PeerConnectionImpl.h:371

RESOLVED INVALID

Status

()

Core
WebRTC: Signaling
P2
critical
RESOLVED INVALID
5 years ago
5 years ago

People

(Reporter: posidron, Unassigned)

Tracking

(Blocks: 1 bug, {crash, testcase})

Trunk
x86_64
Mac OS X
crash, testcase
Points:
---
Bug Flags:
in-testsuite ?

Firefox Tracking Flags

(Not tracked)

Details

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

Attachments

(3 attachments, 1 obsolete attachment)

(Reporter)

Description

5 years ago
Created attachment 661446 [details]
testcase

!!! Real PeerConnection constructor called OMG !!!

!!! {b827e3b0-c1cb-d243-829e-e5ef6150aace} : calling initialize
!!! Queue for {b827e3b0-c1cb-d243-829e-e5ef6150aace} is currently: []
!!! Queue for {b827e3b0-c1cb-d243-829e-e5ef6150aace} is currently: []
!!! mozPeerConnection constructor called [object Window @ 0x11b6378e0 (native @ 0x11b65f0d0)]
!!! {b827e3b0-c1cb-d243-829e-e5ef6150aace} : connect() called
PeerConnectionImpl::Connect()
PeerConnectionImpl::Connect() returned
PeerConnectionImpl::ConnectThread() finished
!!! {b827e3b0-c1cb-d243-829e-e5ef6150aace} : connect() returned
!!! {b827e3b0-c1cb-d243-829e-e5ef6150aace} : createOffer called
!!! {b827e3b0-c1cb-d243-829e-e5ef6150aace} : queued createOffer
!!! Queue for {b827e3b0-c1cb-d243-829e-e5ef6150aace} is currently: [createOffer,]
!!! {b827e3b0-c1cb-d243-829e-e5ef6150aace} : createOffer returned
OnMessage: mChannel 0x0 mConnection 0x10c88b850
PeerConnectionImpl:: got NotifyConnection
Delivering PeerConnection onconnection
!!! {b827e3b0-c1cb-d243-829e-e5ef6150aace} : onConnection called
!!! in executeNext: !!! Queue for {b827e3b0-c1cb-d243-829e-e5ef6150aace} is currently: [createOffer,]
Assertion failure: mIceState != kIceGathering, at /Users/cdiehl/Code/Mozilla/mc-alder/media/webrtc/signaling//./src/peerconnection/PeerConnectionImpl.h:371
(Reporter)

Comment 1

5 years ago
Created attachment 661447 [details]
callstack
(Reporter)

Comment 2

5 years ago
Created attachment 661780 [details]
testcase

The threads mixed up my fuzzing output. This is the correct testcase for the bug.
Attachment #661446 - Attachment is obsolete: true
(Reporter)

Updated

5 years ago
Blocks: 792125

Updated

5 years ago
Whiteboard: [WebRTC] → [WebRTC], [blocking-webrtc+]

Updated

5 years ago
Priority: -- → P1

Updated

5 years ago
Priority: P1 → P2

Updated

5 years ago
Flags: in-testsuite?
Created attachment 673108 [details] [diff] [review]
crashtest v1

Crashtest for original testcase which seems to have been fixed meanwhile. I can't get the browser to crash anymore. But verified that it crashes with an alder nightly build from Sep 15th.
Attachment #673108 - Flags: review?(rjesup)
so the reason why we do not see the crash is that mozPeerConnection has been moved to mozRTCPeerConnection and there is no connect() method available. Jesup, is this bug invalid now?
Flags: needinfo?(rjesup)
Comment on attachment 673108 [details] [diff] [review]
crashtest v1

Review of attachment 673108 [details] [diff] [review]:
-----------------------------------------------------------------

Given how much the API and code has changed since this bug was filed, I don't think this is a useful crashtest to continue to run.  Anything here should be covered by other basic "call basic api function" tests.
Attachment #673108 - Flags: review?(rjesup) → review-
Flags: needinfo?(rjesup)
Agreed, invalid now
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.