Seeing blank pages while accessing all the URL's on chrome Canary-67.0.3393.0 |
|||||
Issue descriptionChrome Version: 67.0.3393.0 OS: Win10, MacOS 10.13.3 & Linux Fedora What steps will reproduce the problem? (1) Launch (Install) new canary build(67.0.3393.0) / Upgrade existing Canary to latest Canary (2) Navigate to any URL (Youtube.com/gmail.com/cnn.com) (3) Observed blank pages (4) Click on Avatar icon on chrom right corner (5) Observed blank popup . Hence unable to sign in What is the expected result? All the pages should be loaded successfully without any crash & should be able to sign in successfully on Canary build. What happens instead? Seeing blank pages while accessing all the URl's on chrome Canary-67.0.3393.0 Please find the attached screencast for reference.Marking it as release block dev as it is seen on latest M67 build. Note: No issue seen on Canary equivalent chrome build-67.0.3393.0 Thanks..!
,
Apr 10 2018
In some cases, it's not just a blank page shown, but only the parts of a page where a script is attempting to run. Experiencing issues like that on google, bing, and wordpress.
,
Apr 10 2018
Crash id generated while accessing gmail.com. a7e93ec2edddb645 Stack trace: ------------ Thread 2 (id: 508531) CRASHED [Simulated Exception @ 0x000000010c744dcb ] MAGIC SIGNATURE THREAD Stack Quality84%Show frame trust levels 0x000000010c744dcb (Google Chrome Framework -crashpad.cc:256 ) crash_reporter::DumpWithoutCrashing() 0x0000000109e3f251 (Google Chrome Framework -dump_without_crashing.cc:23 ) base::debug::DumpWithoutCrashing() 0x000000010868f0ee (Google Chrome Framework -browser_message_filter.cc:180 ) content::BrowserMessageFilter::ShutdownForBadMessage() 0x000000010890ca1e (Google Chrome Framework -render_frame_message_filter.cc:505 ) content::RenderFrameMessageFilter::GetCookies(int, GURL const&, GURL const&, base::OnceCallback<void (std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)>) 0x0000000107edeec8 (Google Chrome Framework -render_frame_message_filter.mojom.cc:733 ) content::mojom::RenderFrameMessageFilterStubDispatch::AcceptWithResponder(content::mojom::RenderFrameMessageFilter*, mojo::Message*, std::__1::unique_ptr<mojo::MessageReceiverWithStatus, std::__1::default_delete<mojo::MessageReceiverWithStatus> >) 0x000000010890da85 (Google Chrome Framework -render_frame_message_filter.mojom.h:175 ) content::mojom::RenderFrameMessageFilterStub<mojo::RawPtrImplRefTraits<content::mojom::RenderFrameMessageFilter> >::AcceptWithResponder(mojo::Message*, std::__1::unique_ptr<mojo::MessageReceiverWithStatus, std::__1::default_delete<mojo::MessageReceiverWithStatus> >) 0x0000000109f2c887 (Google Chrome Framework -interface_endpoint_client.cc:394 ) mojo::InterfaceEndpointClient::HandleValidatedMessage(mojo::Message*) 0x000000010a1959fd (Google Chrome Framework -ipc_mojo_bootstrap.cc:821 ) IPC::(anonymous namespace)::ChannelAssociatedGroupController::Accept(mojo::Message*) 0x0000000109f2aa7a (Google Chrome Framework -connector.cc:443 ) mojo::Connector::ReadSingleMessage(unsigned int*) 0x0000000109f2b0c0 (Google Chrome Framework -connector.cc:472 ) mojo::Connector::ReadAllAvailableMessages() 0x0000000109f3dd77 (Google Chrome Framework -callback.h:124 ) mojo::SimpleWatcher::OnHandleReady(int, unsigned int, mojo::HandleSignalsState const&) 0x0000000109e407b6 (Google Chrome Framework -callback.h:95 ) base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) 0x0000000109e65df3 (Google Chrome Framework -message_loop.cc:354 ) base::MessageLoop::RunTask(base::PendingTask*) 0x0000000109e662c7 (Google Chrome Framework -message_loop.cc:364 ) base::MessageLoop::DoWork() 0x0000000109e67513 (Google Chrome Framework -message_pump_libevent.cc:210 ) base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) 0x0000000109e8c294 (Google Chrome Framework -run_loop.cc:130 ) <name omitted> 0x00000001087c09c3 (Google Chrome Framework -browser_process_sub_thread.cc:155 ) content::BrowserProcessSubThread::IOThreadRun(base::RunLoop*) 0x0000000109ebdc3b (Google Chrome Framework -thread.cc:338 ) base::Thread::ThreadMain() 0x0000000109ebbb86 (Google Chrome Framework + 0x02157b86 ) base::(anonymous namespace)::ThreadFunc(void*) 0x00007fff76a8e6c0 (libsystem_pthread.dylib + 0x000036c0 ) _pthread_body 0x00007fff76a8e56c (libsystem_pthread.dylib + 0x0000356c ) _pthread_start 0x00007fff76a8dc5c (libsystem_pthread.dylib + 0x00002c5c ) thread_start 0x0000000109ebbb2f (Google Chrome Framework + 0x02157b2f ) base::PlatformThread::Detach(base::PlatformThreadHandle) Variations on Windows : ------------------- Good build: ----------- c134752e-b8b72c88 5f419cc9-ca7d8d80 a6674cf-ca7d8d80 3095aa95-3f4a17df 47e5d3db-3d47f4f4 125b7f68-65bced95 4dc30737-b8a5ea08 f9884634-659882c0 44827ee5-43146c13 4b61504a-c9eb6633 9773d3bd-f23d1dea 9e5c75f1-1039a221 f79cb77b-3f4a17df 4ea303a6-ecbb250e 7aa46da5-c946b150 58a025e3-c2b41702 f242806f-5810b593 4bc337ce-69465896 17507c76-ca7d8d80 494d8760-52325d43 f47ae82a-746c2ad4 3ac60855-3ec2a267 f296190c-a5822863 4442aae2-a90023b1 ed1d377-e1cc0f14 12e17bc5-e1cc0f14 75f0f0a0-e1cc0f14 e2b18481-a5822863 e7e71889-4ad60575 98426e68-ca7d8d80 Bad build: c134752e-6d5b49a5 411b6d4e-f23d1dea fe69e053-94941f92 5f419cc9-ca7d8d80 a6674cf-f22a02fa f113d3c9-63942421 9041608a-3f4a17df 1e528f0f-3b7f37f3 b130ecb8-2e32ee7e 6025934e-3f4a17df c27fec31-c982d8da 7c1bc906-b5809d46 3eb101d6-3f4a17df 47e5d3db-3d47f4f4 125b7f68-65bced95 41e765a5-3f4a17df f15c1c09-ca7d8d80 f9884634-659882c0 3042ad4b-cf4f6ead 591576c8-a8bffb1 e56c5101-3f4a17df ceff87ec-3f4a17df 44827ee5-43146c13 4b61504a-a8ff754b 5485fc4d-3d47f4f4 ef05a96e-47945357 9773d3bd-ca7d8d80 93731dca-e89d496c 8fa604e0-ca7d8d80 a428bf14-ff7adebf 9e5c75f1-e406a769 350fabdd-1cf80f06 f79cb77b-3f4a17df 4ea303a6-2e28860d b19465ab-ca7d8d80 bcc34a89-a800dd45 d92562a9-65bced95 7aa46da5-c946b150 2b33233e-d8253d6f 14c5a050-ca7d8d80 2c1d398c-f23d1dea 6973a1cf-f23d1dea 1d085b67-1410f10 ad6d27cc-c6d02f41 2a32876a-ca7d8d80 f242806f-5810b593 4d17cf02-ca7d8d80 f3ea30a0-ad39de72 23496387-232b3cab 344833e9-473e8c2e 4bc337ce-69465896 57789a80-ca7d8d80 9a2f4e5b-f46d6bfd 9b8b36ce-3f4a17df 494d8760-52325d43 3ac60855-3ec2a267 f296190c-71ff9dce 4442aae2-7158671e ed1d377-e1cc0f14 12e17bc5-e1cc0f14 75f0f0a0-a5822863 e2b18481-4c073154 e7e71889-4ad60575 6c05ec0-3f4a17df bbb8f811-3f4a17df 98426e68-ca7d8d80 cc73f8a1-f23d1dea 8834fcca-cf4f6ead 81c6897f-870290a7 493ac2c5-ca7d8d80 Note: 1. This issue is not seen on Canary equivalent signed/unsigned build-67.0.3393.0 hence it is difficult to bisect, marked as Untriaged. Could someone from dev team please take a look into this issue ASAP. 2. No issue seen on Debian Rodate Thanks..!
,
Apr 10 2018
Based on the above crashid and stack trace suspecting this could be same as Issue 831082.
,
Apr 10 2018
,
Apr 10 2018
I'm getting the same, but instead of blank pages, 2 types of errors: - Aw Snap! Something went wrong while trying to display this web page. - Aw Snap! The browser ran out of memory. I suggest you edit the title, as I almost glossed over this and created a new issue, as I'm not seeing blank pages. Version 67.0.3393.0 (Official Build) canary (64-bit).
,
Apr 10 2018
By the 2nd error message, I meant: "Not enough memory to open this page" "Try closing other tabs or programmes to free up memory." (I have 16 GB DDR4 3600 MHz, never got this error until past couple days) Also if I hit refresh a couple times, the page might finally load up, although appears to be slower than usual.
,
Apr 10 2018
Raising to P0 as Canary seems to be unusable as this opens blank pages and crashes randomly (Related bug 831082). lukasza@, could you ptal and mark as dupe of 831082 if needed? Comment #7 could be related to bug 831127.
,
Apr 10 2018
,
Apr 10 2018
This has the same crash signature (*) and started happening in the same version (67.0.3393.0) as issue 831082. (*) [Renderer kill 79] content::RenderFrameMessageFilter::GetCookies |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by trinityx...@gmail.com
, Apr 10 2018