New issue
Advanced search Search tips

Issue 912297 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

DevTools disconnected when stepping through code of React-Redux app

Reported by philip.l...@snapengage.com, Dec 5

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36

Steps to reproduce the problem:
1. Open devtools SOURCE tab
2. Set a breakpoint and run app
3. Step through breakpoints and wait for DevTools "disconnected" error

What is the expected behavior?
* Stepping through does not cause devtools to crash

What went wrong?
Since upgrading from v68 both v69, 70, and 71 (Canary) all crash when debugging my application when breakpoints are set.  This happens Regularly whether or not I add/remove breakpoints, or just step through existing.  

Did this work before? Yes 68

Chrome version: 70.0.3538.110  Channel: n/a
OS Version: OS X 10.14.1
Flash Version: 

GIF: http://recordit.co/zFOHQf5WoV
 
zFOHQf5WoV.gif
2.2 MB View Download
Labels: Needs-Feedback
Has the page crashed? If yes, can you please check chrome://crashes and post the corresponding server crash id here. Thank you.

Comment 2 Deleted

Project Member

Comment 3 by sheriffbot@chromium.org, Dec 5

Cc: alph@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Also, this is when it's in LOCALHOST, not a staging/production environment.  I noticed that if I save changes, and the source code changes, is when it will create the error.

Local Crash ID be781ceb-6b5c-4395-a1e4-899403aedaea

(still being uploaded it says)
Labels: Needs-Feedback
Thanks for the quick response. Please post the server id once it uploads.
oh I see - 
Uploaded Crash Report ID abf5e1d8a9cba25f (Local Crash ID: be781ceb-6b5c-4395-a1e4-899403aedaea)
Project Member

Comment 7 by sheriffbot@chromium.org, Dec 5

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Bisect Needs-Triage-M70
Mergedinto: 902832
Status: Duplicate (was: Unconfirmed)
Thank you. Here's the callstack:

	0x000000010de4ce9c	(Google Chrome Framework -heap_page.h:923 )	blink::HeapAllocator::BackingFree(void*)
0x00000001117bf493	(Google Chrome Framework -vector.h:509 )	blink::MutationObserver::Deliver()
0x00000001117bfa67	(Google Chrome Framework -mutation_observer.cc:365 )	blink::MutationObserver::DeliverMutations()
0x0000000111363c09	(Google Chrome Framework -callback.h:99 )	blink::MicrotaskFunctionCallback(void*)
0x000000010dbc487c	(Google Chrome Framework -runtime-promise.cc:96 )	v8::internal::Runtime_RunMicrotaskCallback(int, v8::internal::Object**, v8::internal::Isolate*)
0x000000010de2038d	(Google Chrome Framework + 0x01dd538d )	v8_Default_embedded_blob_
0x000000010dda2e8d	(Google Chrome Framework + 0x01d57e8d )	v8_Default_embedded_blob_
0x000000203d2052dd		
0x000000010d903d91	(Google Chrome Framework -simulator.h:113 )	v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, bool, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*, v8::internal::Handle<v8::internal::Object>, v8::internal::Execution::MessageHandling, v8::internal::Execution::Target)
0x000000010d904011	(Google Chrome Framework -execution.cc:191 )	v8::internal::Execution::TryCall(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*, v8::internal::Execution::MessageHandling, v8::internal::MaybeHandle<v8::internal::Object>*, v8::internal::Execution::Target)
0x000000010d904133	(Google Chrome Framework -execution.cc:272 )	v8::internal::Execution::RunMicrotasks(v8::internal::Isolate*, v8::internal::Execution::MessageHandling, v8::internal::MaybeHandle<v8::internal::Object>*)
0x000000010da17de1	(Google Chrome Framework -isolate.cc:3973 )	v8::internal::Isolate::RunMicrotasks()
0x0000000111363b99	(Google Chrome Framework -microtask.cc:44 )	blink::Microtask::PerformCheckpoint(v8::Isolate*)
0x00000001110cc690	(Google Chrome Framework -blink_initializer.cc:72 )	blink::(anonymous namespace)::EndOfTaskRunner::DidProcessTask()
0x000000010e4c8280	(Google Chrome Framework -sequence_manager_impl.cc:552 )	base::sequence_manager::internal::SequenceManagerImpl::NotifyDidProcessTask(base::sequence_manager::internal::SequenceManagerImpl::ExecutingTask*, base::sequence_manager::LazyNow*)
0x000000010e4c7eb5	(Google Chrome Framework -sequence_manager_impl.cc:414 )	base::sequence_manager::internal::SequenceManagerImpl::DidRunTask()
0x000000010e4cffcf	(Google Chrome Framework -thread_controller_impl.cc:184 )	base::sequence_manager::internal::ThreadControllerImpl::DoWork(base::sequence_manager::internal::ThreadControllerImpl::WorkType)
0x000000010e466051	(Google Chrome Framework -callback.h:99 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x000000010e483f7d	(Google Chrome Framework -message_loop.cc:434 )	base::MessageLoop::RunTask(base::PendingTask*)
0x000000010e4842e2	(Google Chrome Framework -message_loop.cc:445 )	base::MessageLoop::DoWork()
0x000000010e486819	(Google Chrome Framework -message_pump_mac.mm:455 )	base::MessagePumpCFRunLoopBase::RunWork()
0x000000010e478489	(Google Chrome Framework + 0x0242d489 )	base::mac::CallWithEHFrame(void () block_pointer)
0x000000010e48617e	(Google Chrome Framework -message_pump_mac.mm:431 )	base::MessagePumpCFRunLoopBase::RunWorkSource(void*)
0x00007fff3b55e154	(CoreFoundation + 0x00058154 )	__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__
0x00007fff3b55e0fa	(CoreFoundation + 0x000580fa )	__CFRunLoopDoSource0
0x00007fff3b541b94	(CoreFoundation + 0x0003bb94 )	__CFRunLoopDoSources0
0x00007fff3b54113d	(CoreFoundation + 0x0003b13d )	__CFRunLoopRun
0x00007fff3b540a27	(CoreFoundation + 0x0003aa27 )	CFRunLoopRunSpecific
0x00007fff3d8a73b9	(Foundation + 0x0001c3b9 )	-[NSRunLoop(NSRunLoop) runMode:beforeDate:]
0x000000010e486e7c	(Google Chrome Framework -message_pump_mac.mm:729 )	base::MessagePumpNSRunLoop::DoRun(base::MessagePump::Delegate*)
0x000000010e485c8d	(Google Chrome Framework -message_pump_mac.mm:184 )	base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*)
0x000000010e4a8994	(Google Chrome Framework -run_loop.cc:102 )	<name omitted>
0x0000000112895701	(Google Chrome Framework -renderer_main.cc:200 )	content::RendererMain(content::MainFunctionParams const&)
0x000000010e02f010	(Google Chrome Framework -content_main_runner_impl.cc:898 )	content::ContentMainRunnerImpl::Run(bool)
0x000000010fd0012c	(Google Chrome Framework -main.cc:472 )	service_manager::Main(service_manager::MainParams const&)
0x000000010e02e403	(Google Chrome Framework -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const&)
0x000000010c04ecf2	(Google Chrome Framework -chrome_main.cc:101 )	ChromeMain
0x000000010befeab0	(Google Chrome Helper -chrome_exe_main_mac.cc:101 )	main
0x00007fff6871e08c	(libdyld.dylib + 0x0001708c )	start
Labels: -Needs-Bisect Triaged-ET
As per comment #9, as this issue is merged into issue 902832, removing 'Needs-Bisect' label.

Thanks..
Looks like I don't have access to #902832. How can I be kept up to date?
Components: -Platform>DevTools Blink>MemoryAllocator>GarbageCollection
Labels: M-70
Status: Untriaged (was: Duplicate)
I'm actually not sure if it's the same issue, as issue 902832 seems to be specific to M-72, but this one occurred in M-70. I'm removing the duplicate flag for now.
Issue 912341 has been merged into this issue.

Comment 14 by mlippautz@chromium.org, Jan 16 (6 days ago)

Status: WontFix (was: Untriaged)
Please re-open if this still happens with M71+. There's nothing we can do about M70 anymore.

Comment 15 by philip.l...@snapengage.com, Jan 16 (6 days ago)

as per original submission, it has been happening since upgrading from 68.  It's been visible in 69 & 70.  I will test out 71 and report back if it's still broken

Comment 16 by philip.l...@snapengage.com, Jan 16 (6 days ago)

@mlippautz
please reopen.  I have been on 71 for quite some time now. The 10 most recent Chrome crash Report IDs occurred in 71:

Uploaded Crash Report ID 90fb77c1d426c8f3 (Local Crash ID: abd941cd-f36e-4279-a1d2-24aea2e9fe90)

Uploaded Crash Report ID 1646549d05535ec7 (Local Crash ID: a025265e-3e3a-4f40-aa53-f8669e2c9f03)

Uploaded Crash Report ID a9064c11a6e64d6a (Local Crash ID: 50a3483b-7d5a-428c-96a7-e8ea764c908f)

Uploaded Crash Report ID c41510629149e7c4 (Local Crash ID: e87e2e4b-98c2-435d-9e81-97a709937262)

Uploaded Crash Report ID b64e856a5c0351e1 (Local Crash ID: 8661f8b5-3769-4787-9240-78996f1f9f91)

Uploaded Crash Report ID 18d16f46e6055cf1 (Local Crash ID: 3cd6c1a2-2dfb-487b-9170-c8ba4ef2dd36)

Uploaded Crash Report ID ab2425a688ab7c7c (Local Crash ID: 1c66d24f-2c87-4c84-9add-e48c55c8c555)

Uploaded Crash Report ID bc1bc553b24b5fa0 (Local Crash ID: 50667894-3678-4b57-b12d-d632c1150adf)

Uploaded Crash Report ID c96c8bda457af7e1 (Local Crash ID: ee599173-b08d-4d1f-a5fd-ef1259ba8b59)

Uploaded Crash Report ID a2e17c0636101406 (Local Crash ID: 19deecc7-8642-4224-b3b4-fbc351ea0a5d)

Uploaded Crash Report ID d6c0e32ad0fb0358 (Local Crash ID: b56676f3-aa9f-4a65-8df3-156b3bc143d3)

Sign in to add a comment