This crash usually indicates some kind of filesystem corruption. I'd recommend you run Disk Utility's Repair Disk function to be safe.

Thread 20 Crashed:: Chrome_HistoryThread
0   com.google.Chrome.framework   	0x0000000104e0c849 btreeInitPage + sqlite3.c:56990
1   com.google.Chrome.framework   	0x0000000104e2f2cf getAndInitPage + sqlite3.c:57238
2   com.google.Chrome.framework   	0x0000000104e2c288 sqlite3BtreeMovetoUnpacked + sqlite3.c:60497
3   com.google.Chrome.framework   	0x0000000104e2e733 handleDeferredMoveto + sqlite3.c:70382
4   com.google.Chrome.framework   	0x0000000104e1e27a sqlite3VdbeExec + sqlite3.c:70439
5   com.google.Chrome.framework   	0x0000000104df0a6e sqlite3_step + sqlite3.c:72467
6   com.google.Chrome.framework   	0x0000000104de38dd sql::Statement::StepInternal(bool) + statement.cc:72
7   com.google.Chrome.framework   	0x0000000104de3a2e sql::Statement::Step() + statement.cc:98
8   com.google.Chrome.framework   	0x000000010581eb32 history::ThumbnailDatabase::GetIconMappingsForPageURL(GURL const&, std::__1::vector<history::IconMapping, std::__1::allocator<history::IconMapping> >*) + thumbnail_database.cc:875
9   com.google.Chrome.framework   	0x000000010581e96f history::ThumbnailDatabase::GetIconMappingsForPageURL(GURL const&, int, std::__1::vector<history::IconMapping, std::__1::allocator<history::IconMapping> >*) + thumbnail_database.cc:839
10  com.google.Chrome.framework   	0x00000001058062f7 history::HistoryBackend::GetFaviconsFromDB(GURL const&, int, std::__1::vector<int, std::__1::allocator<int> > const&, std::__1::vector<favicon_base::FaviconRawBitmapResult, std::__1::allocator<favicon_base::FaviconRawBitmapResult> >*) + vector:425
11  com.google.Chrome.framework   	0x0000000105806143 history::HistoryBackend::GetFaviconsForURL(GURL const&, int, std::__1::vector<int, std::__1::allocator<int> > const&, std::__1::vector<favicon_base::FaviconRawBitmapResult, std::__1::allocator<favicon_base::FaviconRawBitmapResult> >*) + vector:632
12  com.google.Chrome.framework   	0x0000000103784368 base::(anonymous namespace)::PostTaskAndReplyRelay::RunTaskAndPostReply() + ref_counted.h:320
13  com.google.Chrome.framework   	0x000000010371c441 base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) + callback_forward.h:29
14  com.google.Chrome.framework   	0x000000010373ff26 base::MessageLoop::RunTask(base::PendingTask*) + vector:638
15  com.google.Chrome.framework   	0x00000001037401fc base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) + message_loop.cc:422
16  com.google.Chrome.framework   	0x0000000103740543 base::MessageLoop::DoWork() + message_loop.cc:515
17  com.google.Chrome.framework   	0x0000000103742b6d base::MessagePumpCFRunLoopBase::RunWork() + message_pump_mac.mm:302
18  com.google.Chrome.framework   	0x00000001037351aa base::mac::CallWithEHFrame(void () block_pointer) + 
19  com.google.Chrome.framework   	0x00000001037425e4 base::MessagePumpCFRunLoopBase::RunWorkSource(void*) + message_pump_mac.mm:281
20  com.apple.CoreFoundation      	0x00007fffc75b48d1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
21  com.apple.CoreFoundation      	0x00007fffc7595c6c __CFRunLoopDoSources0 + 556
22  com.apple.CoreFoundation      	0x00007fffc7595156 __CFRunLoopRun + 934
23  com.apple.CoreFoundation      	0x00007fffc7594b54 CFRunLoopRunSpecific + 420
24  com.google.Chrome.framework   	0x0000000103742f4f base::MessagePumpCFRunLoop::DoRun(base::MessagePump::Delegate*) + message_pump_mac.mm:526
25  com.google.Chrome.framework   	0x0000000103742a2c base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*) + message_pump_mac.mm:218
26  com.google.Chrome.framework   	0x000000010375e023 base::RunLoop::Run() + run_loop.cc:36
27  com.google.Chrome.framework   	0x0000000103788862 base::Thread::ThreadMain() + lock.h:26
28  com.google.Chrome.framework   	0x0000000103784217 base::(anonymous namespace)::ThreadFunc(void*) + platform_thread_posix.cc:73
29  libsystem_pthread.dylib       	0x00007fffdcda8aab _pthread_body + 180
30  libsystem_pthread.dylib       	0x00007fffdcda89f7 _pthread_start + 286
31  libsystem_pthread.dylib       	0x00007fffdcda81fd thread_start + 13

OP, are you willing to correspond with me to attempt to debug this?  I would be interested to know if running something like:

cat ~/Library/Application\ Support/Google/Chrome/Default/Favicons* >/dev/null

gives an error output not.  I believe it will give an error output, something like "Input/output error", in which case filesystem corruption is almost certainly in place, and Disk Utility is the most likely solution.

Sure,

Let me give you a timeline for what has happened.

Just before I reported the bug I deleted the application and re-downloaded
the entire Chrome application. However, it remembered my login and told me
that google did not shut down correctly so the preference files remained
and I am guessing this may be where the problem lies.

Per the previous reply, the response was that there could be some disk
corruption. Disk Utility did report some issues and is repairing the boot
volume while in recovery mode. It has found an orphaned file inode. It says
to look for lost+found and around the size of the logical volume being
adjusted; "Growing Logical Volume, Resizing Core Storage Logical Volume
structures, Growing file system". I just finished the disk check and have
now rebooted.

The problem remains, again it still remembers my login but crashes
immediately.

If you like we can get on the phone.

Thanks,
Keith

And running that command does show an input/output error:

cat ~/Library/Application\ Support/Google/Chrome/Default/Favicons*

cat: /Users/keith/Library/Application
Support/Google/Chrome/Default/Favicons: Input/output error