dkurtz@ Thanks for filing this issue, By observing your chrome version it looks like you are using older version of chrome M52. Could you please upgrade your chrome to latest stable version of M58-58.0.3029.110 and recheck this issue. This should resolve the problem.

Thanks!

Unfortunately the issue still occurs with newer builds of Chrome as well, we've obtained a crash log from a user on Chrome 59:

Chrome 59.0.3071.86
Crash ID 827b4aa4-4bcd-425f-af3d-1acf224d5ade (Server ID: 3c184f29f0000000)

I'm requesting debug logs from this crash event as well, but logging is enabled to send diagnostics through to you so if there is any insight you can provide that would be appreciated.

Thank you for providing more feedback. Adding requester "brajkumar@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

Debug log output: 

[4448:1152:0608/005944.737:ERROR:cache_util_win.cc(20)] Unable to move the cache: 5
[4448:1152:0608/005944.737:ERROR:cache_util.cc(134)] Unable to move cache folder C:\Users\2127805\AppData\Local\Google\Chrome\User Data\ShaderCache\GPUCache to C:\Users\2127805\AppData\Local\Google\Chrome\User Data\ShaderCache\old_GPUCache_000
[4448:1152:0608/005944.737:ERROR:disk_cache.cc(132)] Unable to create cache
[4448:1152:0608/005944.737:ERROR:shader_disk_cache.cc(604)] Shader Cache Creation failed: -2
[4448:1152:0608/005944.784:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.

That log sounds like the on-disk shader cache is still in use for some reason. However, I doubt this is the cause of the renderer process crashes.

Looking at crash ID 3c184f29f0000000, the cause is a simple out-of-memory error. See stack trace below.

I suspect that Salesforce's web app is consuming a lot of memory for these customer chat sessions. Have you asked the customer to profile it in their environment using DevTools?

Stack Quality80%Show frame trust levels
0x74fa80d7	(KERNELBASE.dll + 0x000080d7 )	RaiseException
0x1082479e	(chrome_child.dll -partitions.cpp:143 )	WTF::PartitionsOutOfMemoryUsing128M
0x1082473d	(chrome_child.dll -partitions.cpp:185 )	WTF::Partitions::HandleOutOfMemory()
0x10281478	(chrome_child.dll -partition_alloc.cc:266 )	base::PartitionOutOfMemory
0x0fc1b15f	(chrome_child.dll -partition_alloc.cc:818 )	base::PartitionAllocSlowPath(base::PartitionRootBase *,int,unsigned int,base::PartitionBucket *)
0x0fe32d82	(chrome_child.dll -partitionallocator.h:48 )	WTF::PartitionAllocator::AllocateExpandedVectorBacking<blink::MimeClassInfo>(unsigned int)
0x0f994450	(chrome_child.dll -vector.h:373 )	WTF::VectorBufferBase<blink::CSSParserToken,1,WTF::PartitionAllocator>::AllocateBuffer(unsigned int)
0x0f556dd2	(chrome_child.dll -csstokenizer.cpp:34 )	blink::CSSTokenizer::CSSTokenizer(WTF::String const &)
0x0f9c53b3	(chrome_child.dll -cssparserimpl.cpp:228 )	blink::CSSParserImpl::ParseStyleSheet(WTF::String const &,blink::CSSParserContext const *,blink::StyleSheetContents *,bool)
0x0f33abe8	(chrome_child.dll -stylesheetcontents.cpp:375 )	blink::StyleSheetContents::ParseAuthorStyleSheet(blink::CSSStyleSheetResource const *,blink::SecurityOrigin const *)
0x0f33b06f	(chrome_child.dll -linkstyle.cpp:148 )	blink::LinkStyle::SetCSSStyleSheet(WTF::String const &,blink::KURL const &,blink::ReferrerPolicy,WTF::String const &,blink::CSSStyleSheetResource const *)
0x0f671e23	(chrome_child.dll -cssstylesheetresource.cpp:112 )	blink::CSSStyleSheetResource::DidAddClient(blink::ResourceClient *)
0x0f7660bb	(chrome_child.dll -resource.cpp:738 )	blink::Resource::AddClient(blink::ResourceClient *,blink::Resource::PreloadReferencePolicy)
0x0f33cac6	(chrome_child.dll -resourceowner.h:82 )	blink::ResourceOwner<blink::StyleSheetResource,blink::StyleSheetResourceClient>::SetResource(blink::StyleSheetResource *,blink::Resource::PreloadReferencePolicy)
0x0f33b897	(chrome_child.dll -linkstyle.cpp:338 )	blink::LinkStyle::LoadStylesheetIfNeeded(blink::LinkRequestBuilder const &,WTF::String const &)
0x0f33b62f	(chrome_child.dll -linkstyle.cpp:381 )	blink::LinkStyle::Process()
0x0f33badd	(chrome_child.dll -htmllinkelement.cpp:201 )	blink::HTMLLinkElement::InsertedInto(blink::ContainerNode *)
0x0f38ef3c	(chrome_child.dll -containernode.cpp:748 )	blink::ContainerNode::NotifyNodeInsertedInternal(blink::Node &,blink::HeapVector<blink::Member<blink::Node>,11> &)
0x0f38dab3	(chrome_child.dll -containernode.cpp:233 )	blink::ContainerNode::InsertNodeVector<blink::ContainerNode::AdoptAndAppendChild>(blink::HeapVector<blink::Member<blink::Node>,11> const &,blink::Node *,blink::ContainerNode::AdoptAndAppendChild const &)
0x0f40b84b	(chrome_child.dll -node.cpp:448 )	blink::Node::appendChild(blink::Node *,blink::ExceptionState &)
0x0f40b671	(chrome_child.dll -v8node.cpp:576 )	blink::NodeV8Internal::appendChildMethodForMainWorld
0x0f40b5f0	(chrome_child.dll -v8node.cpp:856 )	blink::V8Node::appendChildMethodCallbackForMainWorld(v8::FunctionCallbackInfo<v8::Value> const &)
0x0f40abc9	(chrome_child.dll -builtins-api.cc:111 )	v8::internal::`anonymous namespace'::HandleApiCallHelper<0>
0x0f40a8ea	(chrome_child.dll -builtins-api.cc:140 )	v8::internal::Builtin_Impl_HandleApiCall
0x0f40a842	(chrome_child.dll -builtins-api.cc:128 )	v8::internal::Builtin_HandleApiCall(int,v8::internal::Object * *,v8::internal::Isolate *)

Can you provide documentation on how to best profile this with DevTools?

Also, can you review another crash to confirm if this is the same:

Crash ID af6fde6b-b568-4b1f-bc89-2d57faa865e8 (Server ID: f324ac1e40000000)

Previously the client was on 32-bit with 4gb ram, they have upgraded to 64-bit with 8gb but still occasionally receive the snap error.

Thank you for providing more feedback. Adding requester "hdodda@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

The stack trace provided in comment #7 looks similar to issue id: 703029. Hence, merging into issue id: 703029.

Thanks...!!

It appears 703029 is not accessible to me, I get the following message:

"You do not have permission to view the requested page. 

Reason: User is not allowed to view this issue"

Is it possible to open up access to this issue?

Wanted to follow up, still unable to access issue 703029