I think crashing is a reasonable thing to do here - given the name of the URL, this is presumably a response that expands to something larger than the renderer can handle. Unfortunately, memory is a finite resource, and we can't render a page that doesn't fit in memory.

That having been said, looks like we're crashing in V8, but crash does not look like a standard OOM stack trace, so maybe something else going on there.


0x000007fed436e84f	(chrome_child.dll -platform-win32.cc:848 )	v8::base::OS::Abort()
0x000007fed32e56c2	(chrome_child.dll -logging.cc:126 )	V8_Fatal
0x000007fed2d68e1e	(chrome_child.dll -escape-analysis.cc:864 )	v8::internal::compiler::EscapeStatusAnalysis::CheckUsesForEscape(v8::internal::compiler::Node *,v8::internal::compiler::Node *,bool)
0x000007fed33b5894	(chrome_child.dll -escape-analysis.cc:691 )	v8::internal::compiler::EscapeStatusAnalysis::Process(v8::internal::compiler::Node *)

OOM.