Also, displayed when launched with various debug statements:

[0103/164001.211698:ERROR:nacl_sandbox_linux.cc(241)] The seccomp-bpf sandbox is not engaged for NaCl: this is dangerous.
[22396,3597598592:16:40:01.230486] Native Client module will be loaded at base address 0x0000188300000000
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
NOT SANDBOXED
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.

it's unlikely that those console messages are related to this issue. will take a look tomorrow to make sure.

Are you capable of recording a trace from chrome://tracing while experiencing this issue?  That would help a lot.

Yes, I can. Just a couple quick questions about tracing.

Is there a specific category I should use? Also, with tracing, where does it write output to, as I said, I must kill chrome when it stops responding, so is there a place it will record output to, without me choosing the save option?

Try starting chrome with the --trace-to-file command line switch. You can also use --trace-to-file-name=filename to specify a filename other than 
trace.json. 

When you record this way you don't need to specify a category, it uses a reasonable deafault.

Thanks for helping us investigate.

Sorry this is becoming such a task. I tried the following:

google-chrome(-unstable) --trace-to-file
google-chrome(-unstable) --trace-to-file --trace-to-file-name=/tmp/chrome.dbg
google-chrome(-unstable) --trace-to-file-name=/tmp/chrome.dbg

and I don't seem to be getting output into that file. 

I did attempt a:

google-chrome(-unstable) --trace-to-console

and that definitely appeared to output trace information to the console (redirecting that to a file ended up creating a very large file, very quickly)

Also, not sure if it helps. But it looks like Chrome created this, last time it crashed:   Crash ID: crash/49fcf51080000000

It is possible that the crash/hang is preventing the tracing from working.  It was not clear from the initial report that you were also getting crashes.  The crash ID information is actually very helpful and might be enough.

Triaging to the Metrics component, which is where the crash is occurring.

Internals>Metrics -> Internals>Tracing

RE: determining whether the
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js, is invoked via document.write.
message is related to the lock-up, could you try to launch chrome with:
--blink-settings=disallowFetchForDocWrittenScriptsInMainFrame=false
and see if the hang goes away? If it goes away w/ that flag then the hang is related to the message, else it is unrelated.

RE: --blink-settings=disallowFetchForDocWrittenScriptsinMainFrame=false

Launched chrome with this flag, and I was able to get it to lock up, just as before.

Also, just for a list of crash reports from Chrome, today, I have the following crash reports:

Crash ID Chrome (Server ID: 07007b1080000000)

Automatically reported Wednesday, January 4, 2017 at 2:05:52 PM

Crash ID Chrome (Server ID: 49fcf51080000000)

Automatically reported Wednesday, January 4, 2017 at 9:42:29 AM

Crash ID Chrome (Server ID: f3aa751080000000)

Automatically reported Wednesday, January 4, 2017 at 9:36:20 AM

Crash ID Chrome (Server ID: 9d53194480000000)

Automatically reported Wednesday, January 4, 2017 at 9:28:46 AM

Crash ID Chrome (Server ID: 16b48a5300000000)

Automatically reported Wednesday, January 4, 2017 at 8:14:32 AM

Crash ID Chrome (Server ID: 2273d24480000000)

Automatically reported Tuesday, January 3, 2017 at 1:36:50 PM

Removing blocking bug given issue persists with doc.write blocking disabled.

crash/861850c480000000

crash/27dc3e9080000000

crash/f11b105080000000

all related.

The stack trace of the crash id 861850c480000000 is as follows:

Thread 0 CRASHED [SIGSEGV @ 0x00000040 ] MAGIC SIGNATURE THREAD
Stack Quality80%Show frame trust levels
0x000056167f5bdd1c	(chrome -./out/Release/../../chrome/browser/browser_process_impl.cc:560 )	BrowserProcessImpl::profile_manager()
0x000056167f3d6bcc	(chrome -./out/Release/../../chrome/browser/profiles/profile_statistics.cc:103 )	ProfileStatistics::SetProfileStatisticsToAttributesStorage(base::FilePath const&, std::string const&, int)
0x000056167f3d6fc3	(chrome -./out/Release/../../chrome/browser/profiles/profile_statistics_aggregator.cc:146 )	ProfileStatisticsAggregator::StatisticsCallback(char const*, ProfileStatisticsAggregator::ProfileStatValue)
0x000056167ec4e05f	(chrome -./out/Release/../../base/callback.h:85 )	void base::internal::ReplyAdapter<ProfileStatisticsAggregator::ProfileStatValue, ProfileStatisticsAggregator::ProfileStatValue>(base::Callback<void (ProfileStatisticsAggregator::ProfileStatValue), (base::internal::CopyMode)1, (base::internal::RepeatMode)1> const&, ProfileStatisticsAggregator::ProfileStatValue*)
0x000056167f699857	(chrome -./out/Release/../../base/callback.h:85 )	base::(anonymous namespace)::RunIfNotCanceledThenUntrack(base::CancellationFlag const*, base::Callback<void (), (base::internal::CopyMode)1, (base::internal::RepeatMode)1> const&, base::Callback<void (), (base::internal::CopyMode)1, (base::internal::RepeatMode)1> const&)
0x000056167f6a4369	(chrome -./out/Release/../../base/callback.h:85 )	base::(anonymous namespace)::PostTaskAndReplyRelay::RunReplyAndSelfDestruct()
0x000056167f6d20cd	(chrome -./out/Release/../../base/callback.h:68 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x000056167f66923f	(chrome -./out/Release/../../base/message_loop/message_loop.cc:421 )	base::MessageLoop::RunTask(base::PendingTask*)
0x000056167f668d34	(chrome -./out/Release/../../base/message_loop/message_loop.cc:430 )	base::MessageLoop::DoWork()
0x000056167f66ac4c	(chrome -./out/Release/../../base/message_loop/message_pump_glib.cc:313 )	base::MessagePumpGlib::Run(base::MessagePump::Delegate*)
0x000056167f68753f	(chrome -./out/Release/../../base/run_loop.cc:37 )	base::RunLoop::Run()
0x000056167ff5228c	(chrome -./out/Release/../../ui/base/x/selection_requestor.cc:279 )	ui::SelectionRequestor::BlockTillSelectionNotifyForRequest(ui::SelectionRequestor::Request*)
0x000056167ff51d19	(chrome -./out/Release/../../ui/base/x/selection_requestor.cc:89 )	ui::SelectionRequestor::PerformBlockingConvertSelection(unsigned long, unsigned long, scoped_refptr<base::RefCountedMemory>*, unsigned long*, unsigned long*)
0x000056167ff524df	(chrome -./out/Release/../../ui/base/x/selection_requestor.cc:119 )	ui::SelectionRequestor::PerformBlockingConvertSelectionWithParameter(unsigned long, unsigned long, std::vector<unsigned long, std::allocator<unsigned long> > const&)
0x000056167ff4ca4f	(chrome -./out/Release/../../ui/base/clipboard/clipboard_aurax11.cc:517 )	ui::ClipboardAuraX11::AuraX11Details::StoreCopyPasteDataAndWait()
0x000056167ff4e5d6	(chrome -./out/Release/../../ui/base/clipboard/clipboard_aurax11.cc:682 )	ui::ClipboardAuraX11::~ClipboardAuraX11()
0x000056167ff45b47	(chrome -./out/Release/../../build/linux/debian_wheezy_amd64-sysroot/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/unique_ptr.h:63 )	ui::Clipboard::DestroyClipboardForCurrentThread()
0x000056167ebb3a95	(chrome -./out/Release/../../content/browser/browser_main_loop.cc:565 )	content::BrowserMainLoop::~BrowserMainLoop()
0x000056167ebb3f88	(chrome -./out/Release/../../content/browser/browser_main_loop.cc:563 )	content::BrowserMainLoop::~BrowserMainLoop()
0x000056167ebbb96d	(chrome -./out/Release/../../build/linux/debian_wheezy_amd64-sysroot/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../include/c++/4.6/bits/unique_ptr.h:63 )	content::BrowserMainRunnerImpl::Shutdown()
0x000056167ebb3832	(chrome -./out/Release/../../content/browser/browser_main.cc:48 )	content::BrowserMain(content::MainFunctionParams const&)
0x000056167f2ec94b	(chrome -./out/Release/../../content/app/content_main_runner.cc:793 )	content::ContentMainRunnerImpl::Run()
0x000056167f2eb40d	(chrome -./out/Release/../../content/app/content_main.cc:20 )	content::ContentMain(content::ContentMainParams const&)
0x000056167df8a5c0	(chrome -./out/Release/../../chrome/app/chrome_main.cc:112 )	ChromeMain
0x00007fa8c5259400	(libc-2.24.so + 0x00020400 )	
0x000056167df78ecf	(chrome + 0x00b38ecf )	SyscallAsm
0x000056167df78d97	(chrome + 0x00b38d97 )	
0x00007fa8cbc21b4a	(ld-2.24.so + 0x00010b4a )	
0x000056167df78d97	(chrome + 0x00b38d97 )	
0x000056167df78dc0	(chrome + 0x00b38dc0 )	_start

The stack trace of this issue looks similar to the issue id: 678186. Hence, merging into the issue id 678186.

Please feel free to undupe, if not the case.