rechecked this issue using chrome version 59.0.3071.115, by updating it over 59.0.3071.109 on Ubuntu 14.04 and Ubuntu 16.04. No crash was observed on updated version of chrome. 

@yaraju: request you to do a system restart, relaunch chrome and try again. Please update us with your observations.

Stack Trace for the Crash ID generated:
=======================================
CRASHED [SIGILL @ 0x0000561b82fdb06c ] MAGIC SIGNATURE THREAD
Stack Quality86%Show frame trust levels
0x0000561b82fdb06c	(chrome -ipc_message_templates.h:117 )	bool IPC::MessageT<ViewMsg_Resize_Meta, std::tuple<content::ResizeParams>, void>::Dispatch<content::RenderWidget, content::RenderWidget, void, void (content::RenderWidget::*)(content::ResizeParams const&)>(IPC::Message const*, content::RenderWidget*, content::RenderWidget*, void*, void (content::RenderWidget::*)(content::ResizeParams const&))
0x0000561b82fd2923	(chrome -render_widget.cc:614 )	content::RenderWidget::OnMessageReceived(IPC::Message const&)
0x0000561b82fc6878	(chrome -render_view_impl.cc:1259 )	content::RenderViewImpl::OnMessageReceived(IPC::Message const&)
0x0000561b806438d9	(chrome -ipc_channel_proxy.cc:329 )	IPC::ChannelProxy::Context::OnDispatchMessage(IPC::Message const&)
0x0000561b801ca1ef	(chrome -callback.h:91 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x0000561b82079c2d	(chrome -task_queue_manager.cc:539 )	blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue(blink::scheduler::internal::WorkQueue*, bool, blink::scheduler::LazyNow, base::TimeTicks*)
0x0000561b82078ff7	(chrome -task_queue_manager.cc:337 )	blink::scheduler::TaskQueueManager::DoWork(bool)
0x0000561b801ca1ef	(chrome -callback.h:91 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x0000561b8015cb0f	(chrome -message_loop.cc:423 )	base::MessageLoop::RunTask(base::PendingTask*)
0x0000561b8015cf37	(chrome -message_loop.cc:434 )	base::MessageLoop::DeferOrRunPendingTask(base::PendingTask)
0x0000561b8015c665	(chrome -message_loop.cc:527 )	base::MessageLoop::DoWork()
0x0000561b8015e2c4	(chrome -message_pump_default.cc:33 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
0x0000561b80179a6d	(chrome -run_loop.cc:37 )	base::RunLoop::Run()
0x0000561b82fe5800	(chrome -renderer_main.cc:200 )	content::RendererMain(content::MainFunctionParams const&)
0x0000561b7fe085be	(chrome -content_main_runner.cc:367 )	content::RunZygote(content::MainFunctionParams const&, content::ContentMainDelegate*)
0x0000561b7fe09584	(chrome -content_main_runner.cc:740 )	content::ContentMainRunnerImpl::Run()
0x0000561b810f8d5f	(chrome -main.cc:179 )	service_manager::Main(service_manager::MainParams const&)
0x0000561b7fe08361	(chrome -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const&)
0x0000561b7ea3d920	(chrome -chrome_main.cc:123 )	ChromeMain
0x00007f7a58d4a82f	(libc-2.23.so + 0x0002082f )	
0x0000561b7ea3d88f	(chrome + 0x00b6488f )	SyscallAsm
0x0000561b7ea3d733	(chrome -os2.cc:103 )	__cxx_global_array_dtor

I have been trying this roughly every time I start my computer since the update, and then when it fails, I go back to using google-chrome-beta for the time being.

Anyhow, I did a system restart just a while ago and launched google-chrome again from commandline. 
Same behavior. Here are the crashes generated:
1ec46c5e40000000
7aac6c5e40000000

Please let me know if you need any other details.

I forgot to add - this time, another thing I tried before launching, is to:

mv ~/.config/google-chrome{,bk}

so that any config-related issues might be avoided. Here's what came up in syslog(dmesg):
[   42.901275] traps: chrome[2963] trap invalid opcode ip:55e6fae97802 sp:7ffd734af290 error:0 in chrome[55e6f5d95000+6adb000]

Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per the crash id in comment #3 and stack trace , this issue is more similar to issue  737961 and hence marking it as duplicate.

Thanks!

I don't have access to the bug 737961 that this was merged into. May I request access to it, or some ability to track it?
Thanks.