wasn't able to repro.

Oh. That jsbin website apparently expires pastes after 8 hours, so the URL in comment 1 no longer works.

Not sure if this is going to show up as an html link in ths bug tracker, but here use this as a URI instead:

data:text/html;base64,PGhlYWQ+CjxsaW5rIHR5cGU9InRleHQvY3NzIiByZWw9InN0eWxlc2hlZXQiIGhyZWY9Imh0dHBzOi8vaHR0cGJpbi5vcmcvZHJpcD9kdXJhdGlvbj02MDAmbnVtYnl0ZXM9NSZjb2RlPTIwMCIvPgo8L2hlYWQ+CmhpCg==

FYI, it seems to crash "Aw, snap!" about 5-15% of the time.  Open ~15 tabs and you're almost guaranteed a crash.

Unable to reproduce the issue on Windows 7 using 50.0.2661.94, latest stable 50.0.2661.102, canary 52.0.2733.0 as per steps in comment #3.

johnkw@Could you please check the issue on clean profile and update the thread with crash report id from chrome://crashes if issue still persists.

Crash ID 499873ec00000000 (beec7060-ca22-451e-9456-fb64e1ea9a75)

Automatically reported Thursday, May 12, 2016 at 8:23:26 AM

Thank you for providing more feedback. Adding requester "ssamanoori@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Can't reproduce the crash (which is listed as a generic renderer hang)

Repro'd again here (took 2 attempts with 15 tabs - got unlucky the first time I guess).

While you're waiting for the tabs to load, can you also reproduce the issue that right-clicking in the window is broken, such that you can't easily get to the "Inspect" menu? (I'm wondering if that's the same bug or if it deserves a different issue tracker filing.)

Stack trace for crash id: 499873ec00000000::
==========================
Thread 0 MAGIC SIGNATURE THREAD
0x77764540	(ntdll.dll + 0x00084540 )	KiFastSystemCallRet
0x77760a99	(ntdll.dll + 0x00080a99 )	NtWaitForSingleObject
0x7490582f	(KERNELBASE.dll + 0x000b582f )	WaitForSingleObjectEx
0x74905771	(KERNELBASE.dll + 0x000b5771 )	WaitForSingleObject
0x0fbee1d4	(chrome_child.dll -waitable_event_win.cc:60 )	base::WaitableEvent::TimedWait(base::TimeDelta const &)
0x0fbed5aa	(chrome_child.dll -message_pump_default.cc:57 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate *)
0x0fbeacaa	(chrome_child.dll -run_loop.cc:35 )	base::RunLoop::Run()
0x0fbeabea	(chrome_child.dll -message_loop.cc:293 )	base::MessageLoop::Run()
0x0fc3d5af	(chrome_child.dll -renderer_main.cc:219 )	content::RendererMain(content::MainFunctionParams const &)
0x0fbe2413	(chrome_child.dll -content_main_runner.cc:395 )	content::RunNamedProcessTypeMain(std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,content::MainFunctionParams const &,content::ContentMainDelegate *)
0x0fbe238f	(chrome_child.dll -content_main_runner.cc:764 )	content::ContentMainRunnerImpl::Run()
0x0fbc7d9d	(chrome_child.dll -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const &)
0x0fbc7a79	(chrome_child.dll -chrome_main.cc:84 )	ChromeMain
0x00ab830b	(chrome.exe -main_dll_loader_win.cc:183 )	MainDllLoader::Launch(HINSTANCE__ *)
0x00ab79a9	(chrome.exe -chrome_exe_main_win.cc:230 )	wWinMain
0x00ae6c79	(chrome.exe -crt0.c:251 )	__tmainCRTStartup
0x7756dea3	(KERNEL32.DLL + 0x0001dea3 )	BaseThreadInitThunk
0x777300bd	(ntdll.dll + 0x000500bd )	__RtlUserThreadStart
0x7773008c	(ntdll.dll + 0x0005008c )	_RtlUserThreadStart

The above stack trace looks similar to bug 336198.Hence, merging it into 336198. Please feel free to un-merge it if not the case.

Issue 336198 won't load ("You do not have permission to view the requested page. "). Is that an open bug?

I don't see any way to reopen this, and it appears to have been market duplicate of something old that's already closed/deleted.

 Issue 614127  has been merged into this issue.

It's probably incorrect to merge this into bug 336198, which is another bug about renderer hangs.

I have many tabs open but I can't repro on two tries. The tab spins for a while, but eventually prints out "hi" and does not crash.

Repro'd again on first attempt. I would add that for some reason it's usually the tab that you opened LAST that crashes. It also seems to be that the crash occurs almost always when one of the other tabs finishes loading or times out.

Now that I've noticed those two things, I've changed my mind, in that it now looks like interaction between tabs is a contributing factor to this crasher bug.

Reproduced by opening data:text/html;base64,PGhlYWQ+CjxsaW5rIHR5cGU9InRleHQvY3NzIiByZWw9InN0eWxlc2hlZXQiIGhyZWY9Imh0dHBzOi8vaHR0cGJpbi5vcmcvZHJpcD9kdXJhdGlvbj02MDAmbnVtYnl0ZXM9NSZjb2RlPTIwMCIvPgo8L2hlYWQ+CmhpCg== in several (>10) tabs:
53.0.2780.0 on Windows 7
53.0.2783.4 on Windows 7

According to the crash signature, this might be related to Issue 615090 (restricted).

Also reproduced on Linux (54.0.2791.0, r404111) by opening the data URL in >15 tabs.

Assigning to dtapuska to determine if this is a duplicate of bug 615090.