New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 757347 link

Starred by 6 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Tab crash is seen on clicking the maps link in Application section of devtools

Project Member Reported by keerthan...@techmahindra.com, Aug 21 2017

Issue description

Chrome Version:62.0.3192.0
OS:Ubuntu 14.04
What steps will reproduce the problem?
(1)Launch chrome and open a fresh profile
(2)Go to Google maps and close it and open NTP with Maps thumbnail
(3)Hit F12 >> Go to Application section>> cache storage and click on the maps link and observe [Refer video]

Expected:Tab should not get crashed
Actual:Instead, tab crash is seen

Crash ids: eec113888c053a50
           67c85082d1a026a3
           d37cd0262f5394b3

This is a Regression issue broken in M-62 
Will update other info soon..


 
Tabcrash.ogv
6.0 MB View Download
Labels: -Needs-Bisect Stability-Crash ReleaseBlock-Stable
Owner: eostroukhov@chromium.org
Status: Assigned (was: Unconfirmed)
Stack Trace:
-------------
Thread 0 (id: 9700) CRASHED [SIGSEGV @ 0x00000008 ] MAGIC SIGNATURE THREAD
Stack Quality76%Show frame trust levels
0x00007f64fecf6d28	(chrome -RefPtr.h:87 )	WTF::String::IsolatedCopy() const
0x00007f64ffde8340	(chrome -BlobData.h:256 )	blink::BlobRegistry::RegisterPublicBlobURL(blink::SecurityOrigin*, blink::KURL const&, WTF::PassRefPtr<blink::BlobDataHandle>)
0x00007f650044dbbc	(chrome -FileReaderLoader.cpp:82 )	blink::FileReaderLoader::Start(blink::ExecutionContext*, WTF::RefPtr<blink::BlobDataHandle>)
0x00007f6501157e68	(chrome -InspectorCacheStorageAgent.cpp:502 )	blink::(anonymous namespace)::CachedResponseMatchCallback::OnSuccess(blink::WebServiceWorkerResponse const&)
0x00007f6500d89386	(chrome -cache_storage_dispatcher.cc:339 )	content::CacheStorageDispatcher::OnCacheStorageMatchSuccess(int, int, content::ServiceWorkerResponse const&)
0x00007f6500d89178	(chrome -tuple.h:56 )	bool IPC::MessageT<CacheStorageMsg_CacheStorageMatchSuccess_Meta, std::__1::tuple<int, int, content::ServiceWorkerResponse>, void>::Dispatch<content::CacheStorageDispatcher, content::CacheStorageDispatcher, void, void (content::CacheStorageDispatcher::*)(int, int, content::ServiceWorkerResponse const&)>(IPC::Message const*, content::CacheStorageDispatcher*, content::CacheStorageDispatcher*, void*, void (content::CacheStorageDispatcher::*)(int, int, content::ServiceWorkerResponse const&))
0x00007f6500d87d19	(chrome -cache_storage_dispatcher.cc:241 )	content::CacheStorageDispatcher::OnMessageReceived(IPC::Message const&)
0x00007f64ffdb57cb	(chrome -worker_thread_message_filter.cc:44 )	content::WorkerThreadMessageFilter::OnMessageReceived(IPC::Message const&)
0x00007f64fda88f3a	(chrome -callback.h:91 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x00007f64fd6938a6	(chrome -task_queue_manager.cc:532 )	blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue(blink::scheduler::internal::WorkQueue*, bool, blink::scheduler::LazyNow, base::TimeTicks*)
0x00007f64fd691918	(chrome -task_queue_manager.cc:330 )	blink::scheduler::TaskQueueManager::DoWork(bool)
0x00007f64fda88f3a	(chrome -callback.h:91 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x00007f64fdaa16ff	(chrome -message_loop.cc:406 )	base::MessageLoop::RunTask(base::PendingTask*)
0x00007f64fdaa1dfb	(chrome -message_loop.cc:417 )	base::MessageLoop::DoWork()
0x00007f64fdaa33f4	(chrome -message_pump_default.cc:33 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
0x00007f64fdac274f	(chrome -run_loop.cc:123 )	base::RunLoop::Run()
0x00007f650119309d	(chrome -renderer_main.cc:220 )	content::RendererMain(content::MainFunctionParams const&)
0x00007f64fd777b47	(chrome -content_main_runner.cc:338 )	content::RunZygote(content::MainFunctionParams const&, content::ContentMainDelegate*)
0x00007f64fd778d8c	(chrome -content_main_runner.cc:693 )	content::ContentMainRunnerImpl::Run()
0x00007f64fd7815ca	(chrome -main.cc:469 )	service_manager::Main(service_manager::MainParams const&)
0x00007f64fd777821	(chrome -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const&)
0x00007f64fc3167a4	(chrome -chrome_main.cc:122 )	ChromeMain
0x00007f64f466df44	(libc-2.19.so + 0x00021f44 )	
0x00007f64fc3166ef	(chrome + 0x017a96ef )	
0x00007f64fc20dfff	(chrome + 0x016a0fff )	
0x00007f64fa9581f2	(ld-2.19.so + 0x000101f2 )	
0x00007f64fc20dfff	(chrome + 0x016a0fff )	
0x00007f64fc20e028	(chrome + 0x016a1028 )	_start
0x00007ffd7dd04547		

Unable to reproduce this crash manually from Chrome TE end, Hence assigning through code search from the above stack trace.

Used code search for the file "InspectorCacheStorageAgent.cpp" from above stack trace and suspecting the below change might be caused this issue.
https://chromium.googlesource.com/chromium/src/+/9e2bedd723e9a4a67e9623861de64c0e5d6d4d2f

eostroukhov@: Could you please check if this is caused with respect to your change, if not please help us in reassign the issue to the right owner. 

Thanks!
NOTE: Issue is reproducible continously when clicked on "og/_/js/k=og.og.en_US.84ccP8dp0MAN.O/rt=j/m=ld,gl,is,id,nb,nw,sb,sd,p,vd,awd,st,lod,eld,ip,dp,cpd/exm=bt,base,bn,bu,cp,el,lo,sbi,ni,sf,up,dd,aw,iw,if,gi,vi,pi,eq,uc/d=1/ed=1/rs=AA2YrTumXztvsiOzxaNN140bTl2K6zrlIw" link like this.. in the Cache storage of application section of devtools	
Labels: -ReleaseBlock-Stable ReleaseBlock-Beta
One of the top crashes in canary- 62.0.3192.0. Please have a fix soon.
Cc: jarin@chromium.org rbasuvula@chromium.org nyerramilli@chromium.org msrchandra@chromium.org yangguo@chromium.org ranjitkan@chromium.org
 Issue 757384  has been merged into this issue.
Project Member

Comment 5 by bugdroid1@chromium.org, Aug 22 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/08279eb0c78f063eb9e53015a6ddb7cf72d9d1bc

commit 08279eb0c78f063eb9e53015a6ddb7cf72d9d1bc
Author: Eugene Ostroukhov <eostroukhov@chromium.org>
Date: Tue Aug 22 17:43:40 2017

[DevTools] No crash when previewing cache entry

Bug:  757347 
Change-Id: I0f085792282a5b1de10a207651c4dcfb6e73293d
Reviewed-on: https://chromium-review.googlesource.com/624937
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Eugene Ostroukhov <eostroukhov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#496358}
[modify] https://crrev.com/08279eb0c78f063eb9e53015a6ddb7cf72d9d1bc/third_party/WebKit/Source/modules/cachestorage/InspectorCacheStorageAgent.cpp

Status: Fixed (was: Assigned)
Labels: TE-Verified-M62 TE-Verified-62.0.3194.0
Above issue is fixed on latest Dev version 62.0.3194.0 for Win and Linux OS ..
Thanks!

Sign in to add a comment