NOTE: Issue is not reproducible on 61.0.3124.4(today's Dev release candidate)

stack Trace:
-------------
Thread 21 (id: 4228) CRASHED [SIGABRT @ 0x000003e800001063 ] MAGIC SIGNATURE THREAD
Stack Quality93%Show frame trust levels
0x00007f188c0c0cc9	(libc-2.19.so -raise.c:56 )	raise
0x00007f188c0c40d7	(libc-2.19.so -abort.c:89 )	abort
0x00005636f5c931f1	(chrome -debugger_posix.cc:258 )	base::debug::BreakDebugger()
0x00005636f5ca85b6	(chrome -logging.cc:783 )	logging::LogMessage::~LogMessage()
0x00005636f60e3941	(chrome -nss_util.cc:679 )	base::LazyInstance<crypto::(anonymous namespace)::NSSInitSingleton, base::internal::LeakyLazyInstanceTraits<crypto::(anonymous namespace)::NSSInitSingleton> >::Get()
0x00005636f5ef56a4	(chrome -singleton.h:55 )	net::CertDatabase::GetInstance()
0x00005636f6043797	(chrome -client_socket_factory.cc:27 )	net::ClientSocketFactory::GetDefaultFactory()
0x00005636f5f50102	(chrome -dns_client.cc:92 )	net::DnsClient::CreateClient(net::NetLog*)
0x00005636f59d0439	(chrome -dns_probe_service.cc:143 )	chrome_browser_net::DnsProbeService::SetSystemClientToCurrentConfig()
0x00005636f59d0361	(chrome -dns_probe_service.cc:86 )	chrome_browser_net::DnsProbeService::DnsProbeService()
0x00005636f5998589	(chrome -io_thread.cc:591 )	IOThread::Init()
0x00005636f494a24b	(chrome -browser_process_sub_thread.cc:42 )	content::BrowserProcessSubThread::Init()
0x00005636f5cf6969	(chrome -thread.cc:327 )	base::Thread::ThreadMain()
0x00005636f5cf2893	(chrome -platform_thread_posix.cc:71 )	base::(anonymous namespace)::ThreadFunc(void*)
0x00007f189246c181	(libpthread-2.19.so + 0x00008181 )	

Tried to reproduce this issue on both corp and non-corp machines, But no luck in reproducing this issue from chrome-TE end.

Used code search for the file "nss_util.cc" from above stack trace and suspecting the below change
Review-Url: https://codereview.chromium.org/2721373002

rsleevi@: Observed some recent changes for the above file, Could you please check if this is caused with respect to your change, if not please help us in reassign the issue to the right owner. 

Thanks!

Are you using the installer or a bisected binary?

 Issue 691261  updates the NSS requirements for important security fixes to NSS 3.26 (runtime check), but sets the installer to 3.28 (RPM based systems) or 3.26 (Debian based systems), based on the current status of our supported Linux platforms and the available security update packages.

If installing via Debian package, this will force an NSS dependency >= 3.26.

However, if manually launching the binary (e.g. without the DEB or RPM), then you will only get the runtime check. This can happen, for example, if bisecting artifacts directly.

keerthana.v@ Could you please respond to the comment #3.

Thank You...

 Somehow this got resolved by updating from Software Updater and now able to launch chrome without any issues

Thank you.. 

Marking as WontFix based on the remarks. Hopefully Comment #3 provides sufficient explanation