Chrome crashing on new offer in WebRTC session

87 views
Skip to first unread message

Uma Shunmugan

unread,
Jan 28, 2014, 12:05:41 PM1/28/14
to discuss...@googlegroups.com
WebRTC sessions are crashing the latest stable Chrome (32.0.1700.102m) whenever processing a new offer (after a session is established).  FYI, this is happening with the latest Canary version as well, and the same application worked fine with the previous Chrome stable version that I had, which was 31.0.1650.63m.  

The crash with "Aw, Snap!" happens when peerConnection.setRemoteDescription is being called [with arguments ( new window.RTCSessionDescription( JSON.parse(message_text)), function () { // some logging }, function () { // error reporting } )].

Here are some messages from the Chrome debug log before the crash (note the "failed for RIDEV_REMOVE: The parameter is incorrect" message):

...
[3376:12944:0127/173211:INFO:CONSOLE(255)] "grtc: 1590.609: processSignalingMessage(type=OFFER, state=established)", source: http://ca-to-umshunmu/webrtc/src/jsapi/classes/grtc.js (255)
[0127/173211:VERBOSE1:ipc_sync_channel.cc(385)] Canceling pending sends
[0127/173211:VERBOSE1:ipc_sync_channel.cc(385)] Canceling pending sends
[0127/173211:VERBOSE1:ipc_sync_channel.cc(385)] Canceling pending sends
[3376:12944:0127/173211:INFO:user_input_monitor_win.cc(166)] RegisterRawInputDevices() failed for RIDEV_REMOVE: The parameter is incorrect.
[3376:10616:0127/173211:VERBOSE1:audio_low_latency_output_win.cc(289)] WASAPIAudioOutputStream::Stop()
[3376:10616:0127/173211:VERBOSE1:audio_low_latency_output_win.cc(326)] WASAPIAudioOutputStream::Close()
[3376:10616:0127/173211:VERBOSE1:audio_low_latency_output_win.cc(289)] WASAPIAudioOutputStream::Stop()
[3376:7260:0127/173212:VERBOSE1:resource_loader.cc(304)] OnResponseStarted: chrome://settings-frame/notifyTimer.js?profile=First%20user&counter=2732
[3376:7260:0127/173212:VERBOSE1:resource_loader.cc(344)] OnReadCompleted: "chrome://settings-frame/notifyTimer.js?profile=First%20user&counter=2732" bytes_read = 0
[3376:7260:0127/173212:VERBOSE1:resource_loader.cc(606)] ResponseCompleted: chrome://settings-frame/notifyTimer.js?profile=First%20user&counter=2732
[3376:7260:0127/173213:VERBOSE1:resource_loader.cc(304)] OnResponseStarted: 

Any help will be greatly appreciated.

Thanks,
 Uma

Vikas

unread,
Jan 28, 2014, 2:04:33 PM1/28/14
to discuss...@googlegroups.com
Hi,

Thanks for the feedback, can you file a bug in here and share the crash id for the crash. You can find information about getting crash id here.

/Vikas

Uma Shunmugan

unread,
Jan 28, 2014, 4:08:18 PM1/28/14
to discuss...@googlegroups.com


Filed issue 338825.  Thanks!
Reply all
Reply to author
Forward
0 new messages