Tested this issue on Mac 10.13.2 & windows using chrome reported version-63.0.3239.132 & stable-64.0.3282.119 & Canary-66.0.3335.0 as per the above steps. Tried to upload ~50 photos into each album & no crash observed in photos.google.com.

As per the above provided crash id, issue seems to be intentional crash. Please find the below stack trace:

Thread 0 (id: 6610367) CRASHED [EXC_BAD_ACCESS / KERN_INVALID_ADDRESS @ 0x00000000 ] MAGIC SIGNATURE THREAD
Stack Quality78%Show frame trust levels
0x000000010f23d020	(Google Chrome Framework -render_frame_impl.cc:743 )	content::CrashIntentionally()
0x000000010f23d2f6	(Google Chrome Framework -render_frame_impl.cc:821 )	content::MaybeHandleDebugURL(GURL const&)
0x000000010f2617e1	(Google Chrome Framework -render_frame_impl.cc:6449 )	content::RenderFrameImpl::PrepareRenderViewForNavigation(GURL const&, content::RequestNavigationParams const&)
0x000000010f24bae1	(Google Chrome Framework -render_frame_impl.cc:5331 )	content::RenderFrameImpl::OnFailedNavigation(content::CommonNavigationParams const&, content::RequestNavigationParams const&, bool, int)
0x000000010f24b9b4	(Google Chrome Framework -tuple.h:52 )	bool IPC::MessageT<FrameMsg_FailedNavigation_Meta, std::__1::tuple<content::CommonNavigationParams, content::RequestNavigationParams, bool, int>, void>::Dispatch<content::RenderFrameImpl, content::RenderFrameImpl, void, void (content::RenderFrameImpl::*)(content::CommonNavigationParams const&, content::RequestNavigationParams const&, bool, int)>(IPC::Message const*, content::RenderFrameImpl*, content::RenderFrameImpl*, void*, void (content::RenderFrameImpl::*)(content::CommonNavigationParams const&, content::RequestNavigationParams const&, bool, int))
0x000000010f242816	(Google Chrome Framework -render_frame_impl.cc:1688 )	content::RenderFrameImpl::OnMessageReceived(IPC::Message const&)
0x000000010b71337a	(Google Chrome Framework -ipc_channel_proxy.cc:320 )	IPC::ChannelProxy::Context::OnDispatchMessage(IPC::Message const&)
0x000000010b3d127b	(Google Chrome Framework -callback.h:64 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x000000010aee6de1	(Google Chrome Framework -task_queue_manager.cc:531 )	blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue(blink::scheduler::internal::WorkQueue*, bool, blink::scheduler::LazyNow, base::TimeTicks*)
0x000000010aee4e31	(Google Chrome Framework -task_queue_manager.cc:322 )	blink::scheduler::TaskQueueManager::DoWork(bool)
0x000000010b3d127b	(Google Chrome Framework -callback.h:64 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x000000010b3f5f43	(Google Chrome Framework -message_loop.cc:394 )	base::MessageLoop::RunTask(base::PendingTask*)
0x000000010b3f6438	(Google Chrome Framework -message_loop.cc:406 )	base::MessageLoop::DoWork()
0x000000010b3f82a9	(Google Chrome Framework -message_pump_mac.mm:452 )	base::MessagePumpCFRunLoopBase::RunWork()
0x000000010b3e9439	(Google Chrome Framework + 0x01c53439 )	base::mac::CallWithEHFrame(void () block_pointer)
0x000000010b3f7bce	(Google Chrome Framework -message_pump_mac.mm:428 )	base::MessagePumpCFRunLoopBase::RunWorkSource(void*)
0x00007fff4a2f2710	(CoreFoundation + 0x0009f710 )	__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
0x00007fff4a3aa39b	(CoreFoundation + 0x0015739b )	__CFRunLoopDoSource0
0x00007fff4a2d56ff	(CoreFoundation + 0x000826ff )	__CFRunLoopDoSources0
0x00007fff4a2d4b7c	(CoreFoundation + 0x00081b7c )	__CFRunLoopRun
0x00007fff4a2d43d6	(CoreFoundation + 0x000813d6 )	CFRunLoopRunSpecific
0x00007fff4c3ceb75	(Foundation + 0x00020b75 )	-[NSRunLoop(NSRunLoop) runMode:beforeDate:]
0x000000010b3f890d	(Google Chrome Framework -message_pump_mac.mm:724 )	base::MessagePumpNSRunLoop::DoRun(base::MessagePump::Delegate*)
0x000000010b3f76ed	(Google Chrome Framework -message_pump_mac.mm:179 )	base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*)
0x000000010b41a4b3	(Google Chrome Framework -run_loop.cc:114 )	<name omitted>
0x000000010f2a49a2	(Google Chrome Framework -renderer_main.cc:220 )	content::RendererMain(content::MainFunctionParams const&)
0x000000010aff5fb9	(Google Chrome Framework -content_main_runner.cc:710 )	content::ContentMainRunnerImpl::Run()
0x000000010c7f1ae9	(Google Chrome Framework -main.cc:469 )	service_manager::Main(service_manager::MainParams const&)
0x000000010aff5563	(Google Chrome Framework -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const&)
0x000000010979966e	(Google Chrome Framework -chrome_main.cc:123 )	ChromeMain
0x000000010977047b	(Google Chrome Helper -chrome_exe_main_mac.cc:165 )	main
0x00007fff71bc3114	(libdyld.dylib + 0x00001114 )	start
0x00007fff71bc3114	(libdyld.dylib + 0x00001114 )	start

Marking it as Untriaged . Could some one from google apps team please take a look.

Thanks..!

That crash report is not related to the bug described.  It's what happens when you type "chrome://crash" into the address bar and the result is a sad tab.  If you don't see other crash IDs in chrome://crashes, then we probably aren't receiving a crash report for it.

I think this is likely what happens when dragging that many images into a page-- it's going to trigger a lot of work, causing the page (or possibly the browser) to become unresponsive.  I'll add a DataTransfer label in case there's any cap worth adding to avoid making the browser unresponsive.

The crash is user-induced, so I removed the crash labels and restrictions. Marking this available, as the Storage team will not be able to get to it in the foreseeable future.