Unable to reproduce the scenario on windows 10 with chrome version #55.0.2883.87
Didn't observe any crash on screen sharing in hangouts.

Attaching the screencast for your reference
mr.kumaraditya@ could you please try the same scenario with clean with profile no apps/extensions and let us know your observations.

Pasting Stack trace for crash id "0397d46080000000"
=============================================
Thread 0 CRASHED [EXCEPTION_ACCESS_VIOLATION_READ @ 0x00000000 ] MAGIC SIGNATURE THREAD
Stack Quality100%Show frame trust levels
0x64eb8aa3	(chrome.dll -skbitmap.cpp:52 )	SkBitmap::operator=(SkBitmap const &)
0x64eb89ff	(chrome.dll -skbitmap.cpp:38 )	SkBitmap::SkBitmap(SkBitmap const &)
0x6533b1a0	(chrome.dll -image_skia.cc:335 )	gfx::ImageSkia::CreateFrom1xBitmap(SkBitmap const &)
0x65fb06fa	(chrome.dll -window_icon_util_win.cc:39 )	GetWindowIcon(content::DesktopMediaID)
0x65f75310	(chrome.dll -desktop_media_list_view.cc:178 )	DesktopMediaListView::OnSourceAdded(DesktopMediaList *,int)
0x65fb0b3c	(chrome.dll -desktop_media_list_base.cc:84 )	DesktopMediaListBase::UpdateSourcesList(std::vector<DesktopMediaListBase::SourceDescription,std::allocator<DesktopMediaListBase::SourceDescription> > const &)
0x65faf188	(chrome.dll -native_desktop_media_list.cc:290 )	NativeDesktopMediaList::RefreshForAuraWindows(std::vector<DesktopMediaListBase::SourceDescription,std::allocator<DesktopMediaListBase::SourceDescription> >)
0x65faf66d	(chrome.dll -bind_internal.h:339 )	base::internal::Invoker<base::internal::BindState<void ( NativeDesktopMediaList::*)(std::vector<DesktopMediaListBase::SourceDescription,std::allocator<DesktopMediaListBase::SourceDescription> >),base::WeakPtr<NativeDesktopMediaList>,std::vector<DesktopMediaListBase::SourceDescription,std::allocator<DesktopMediaListBase::SourceDescription> > >,void >::Run(base::internal::BindStateBase *)
0x64ea3b0f	(chrome.dll -task_annotator.cc:54 )	base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask const &)
0x64e500f2	(chrome.dll -message_loop.cc:405 )	base::MessageLoop::RunTask(base::PendingTask const &)
0x64e50907	(chrome.dll -message_loop.cc:513 )	base::MessageLoop::DoWork()
0x64ea40ce	(chrome.dll -message_pump_win.cc:263 )	base::MessagePumpForUI::DoRunLoop()
0x64ea3df4	(chrome.dll -message_pump_win.cc:141 )	base::MessagePumpWin::Run(base::MessagePump::Delegate *)
0x64e8d76b	(chrome.dll -run_loop.cc:35 )	base::RunLoop::Run()
0x64dda8ef	(chrome.dll -chrome_browser_main.cc:2116 )	ChromeBrowserMainParts::MainMessageLoopRun(int *)
0x64a71c81	(chrome.dll -browser_main_loop.cc:981 )	content::BrowserMainLoop::RunMainMessageLoopParts()
0x64a745dd	(chrome.dll -browser_main_runner.cc:155 )	content::BrowserMainRunnerImpl::Run()
0x64a6fe80	(chrome.dll -browser_main.cc:46 )	content::BrowserMain(content::MainFunctionParams const &)
0x64da2624	(chrome.dll -content_main_runner.cc:779 )	content::ContentMainRunnerImpl::Run()
0x642d36a3	(chrome.dll -chrome_main.cc:97 )	ChromeMain
0x001253bf	(chrome.exe -main_dll_loader_win.cc:174 )	MainDllLoader::Launch(HINSTANCE__ *,base::TimeTicks)
0x00121ad2	(chrome.exe -chrome_exe_main_win.cc:247 )	wWinMain
0x0018a773	(chrome.exe -exe_common.inl:253 )	__scrt_common_main_seh
0x7700ed5b	(KERNEL32.dll + 0x0004ed5b )	BaseThreadInitThunk
0x76ed37ea	(ntdll.dll + 0x000637ea )	__RtlUserThreadStart
0x76ed37bd	(ntdll.dll + 0x000637bd )	_RtlUserThreadStart

Deleted: Issue 678955.mp4 2.2 MB

	Issue 678955.mp4 2.2 MB View Download

We received report from enterprise customer that multiple users are affected by the same issue. 

Chrome version: 55.0.2883.87, 57.0.2971.0 (Canary)
OS version: Windows 10 (CPU: Core i7 2.6 GHZ, RAM: 8 GB)

Recent crash IDs:
0c815c0480000000
39b1a51080000000 (Canary)
821c56d080000000

All these crash reports indicate the issue is crbug.com/599873.

This may be related to 599873

Issue 599873 has been merged into this issue.

As per the magic stack, this looks like a regression in M55. Crash rate in stable seems to be pretty high.

55.0.2883.87	62.42%	3372 reports.

Regression Range
================

https://chromium.googlesource.com/chromium/src/+log/55.0.2853.0..55.0.2861.0?pretty=fuller&n=10000

Link to the builds which introduced the crash:

https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27SkBitmap%3A%3ASkBitmap%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000

Possible suspect
================
https://chromium.googlesource.com/chromium/src/+/8234584f65628f5f8c43341eaaa94dd0b1681f50

Assigning to the Cl owner,not sure whether the above CL is the correct culprit  so looping to skia experts as well.

related to crbug/676758.
A possible cause is that some application without icon is running.
I've made a fix for current chromium and M56.

Is it still feasible and beneficial to request a merge to M55?

If the change is small, I'd like to request a merge. Not sure if there is going to be another build, but if there is, I'd like this to be included in it.  When would the change be available on 56 externally ? We can request the customer to test.

We are not planning any further M55 stable releases as M56 stable launch is coming soon by end of this month.

Thanks for the fix. qiangchen@ would it be possible to add an automated test for the CL to avoid regressions in future.

Reply to #10.The M56 build with the fix will be deployed to Beta on Wednesday 01/18.

Re #12: Automated test is not easy as the function heavily depends on the Windows APIs.