New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 643158 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Gmail and hangouts window crashes on doing hangout video call

Project Member Reported by sc00335...@techmahindra.com, Sep 1 2016

Issue description

Version: 55.0.2844.0
Platform: 8760.0.0 dev channel peach_pit
OS: Chrome

What steps will reproduce the problem?
(1)Sign in to Gmail >> Open any chat try doing/accepting video call and observe

Expected: Gmail and hangouts should not crash on hangouts call
Actual: Instead Gmail and video call window crashes.

Same is working fine with daisy and jerry of 55.0.2844.0/8760.0.0 dev channel peach_pit.

Crash ids: 784302d100000000 , 60bf02d100000000
 
Cc: songsuk@chromium.org tienchang@chromium.org pucchakayala@chromium.org
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Chrome device: peach_pit using Version: 55.0.2844.0 Platform: 8760.0.0 dev. Observed crash while having hangout videos.

Stack Trace for Crash ID: 60bf02d100000000
--------------------------------------------
Thread 14 CRASHED [SIGSEGV @ 0x70747478 ] MAGIC SIGNATURE THREAD
0xb36886e6	(chrome + 0x011dd6e6 )	std::map<unsigned int, webrtc::SendStatisticsProxy::StatsUpdateTimes, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, webrtc::SendStatisticsProxy::StatsUpdateTimes> > >::operator[](unsigned int const&)
0xb368924f	(chrome + 0x011de24f )	webrtc::SendStatisticsProxy::OnSendEncodedImage(webrtc::EncodedImage const&, webrtc::CodecSpecificInfo const*)
0xb368fb61	(chrome + 0x011e4b61 )	webrtc::ViEEncoder::OnEncodedImage(webrtc::EncodedImage const&, webrtc::CodecSpecificInfo const*, webrtc::RTPFragmentationHeader const*)
0xb3692f05	(chrome + 0x011e7f05 )	webrtc::VCMEncodedFrameCallback::OnEncodedImage(webrtc::EncodedImage const&, webrtc::CodecSpecificInfo const*, webrtc::RTPFragmentationHeader const*)
0xb36db19b	(chrome + 0x0123019b )	webrtc::SimulcastEncoderAdapter::OnEncodedImage(unsigned int, webrtc::EncodedImage const&, webrtc::CodecSpecificInfo const*, webrtc::RTPFragmentationHeader const*)
0xb36db1f1	(chrome + 0x012301f1 )	(anonymous namespace)::AdapterEncodedImageCallback::OnEncodedImage(webrtc::EncodedImage const&, webrtc::CodecSpecificInfo const*, webrtc::RTPFragmentationHeader const*)
0xb367d8b1	(chrome + 0x011d28b1 )	webrtc::EncodedImageCallback::Encoded(webrtc::EncodedImage const&, webrtc::CodecSpecificInfo const*, webrtc::RTPFragmentationHeader const*)
0xb5dde555	(chrome + 0x03933555 )	content::RTCVideoEncoder::Impl::ReturnEncodedImage(webrtc::EncodedImage const&, int, unsigned short)
0xb5dde837	(chrome + 0x03933837 )	content::RTCVideoEncoder::Impl::BitstreamBufferReady(int, unsigned int, bool, base::TimeDelta)
0xb2e4f677	(chrome + 0x009a4677 )	media::GpuVideoEncodeAcceleratorHost::OnMessageReceived(IPC::Message const&)
0xb2aa774d	(chrome + 0x005fc74d )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask const&)
0xb2a9960b	(chrome + 0x005ee60b )	base::MessageLoop::DoWork()
0xb2a998b5	(chrome + 0x005ee8b5 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
0xb3d86815	(chrome + 0x018db815 )	base::RunLoop::Run()
0xb3d98359	(chrome + 0x018ed359 )	base::Thread::ThreadMain()
0xb3d962bd	(chrome + 0x018eb2bd )	base::(anonymous namespace)::ThreadFunc(void*)
0xb247a6b9	(libpthread-2.19.so -pthread_create.c:311 )	start_thread
0xb1e8465b	(libc-2.19.so + 0x0009e65b )	clone
Labels: ReleaseBlock-Dev
Marking it as ReleaseBlock-Dev, Please feel free to edit or remove if it's not required.
Cc: jansson@chromium.org vsu...@chromium.org srcv@chromium.org avkodipelli@chromium.org
>> Same is working fine with daisy and jerry of 55.0.2844.0/8760.0.0 dev channel peach_pit.


Do you mean this crash is not reproducible on daisy and jerry, but is reproducible on peach_pit?

Is this reproducible in M54?


Comment 5 by srcv@chromium.org, Sep 1 2016

Mergedinto: 641600
Status: Duplicate (was: Untriaged)
This issue was observed on chrome device Pit with M54 

Marking this issue as a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=641600

Sign in to add a comment