Service Worker: Step-Through debugging stops working after some timeout
Reported by
va...@visionsinteractive.ch,
Nov 8 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.30 Safari/537.36 Steps to reproduce the problem: 1. Develop a website with a service worker that intercepts fetch requests and handles them with an async function (ES7) 2. attempt to debug parts of the service worker, by adding a debugger statement 3. then stepping through the code What is the expected behavior? Step-through debugging and the console always work as intended, no matter if I debug for 10 or 1000 seconds What went wrong? at some point the step-through debugging and the console stops working: i.e. typing anything into the console is ignored and clicking on any button of the debug column buttons ["Resume script execution…", "Step over…", "Step into…", "Step out…"] does nothing, but losing the focus of the debugged line in the source panel (see attached video) Did this work before? N/A Chrome version: 63.0.3239.30 Channel: beta OS Version: 10.0 Flash Version: I assume that it could be related to the timeout of the fetch request in the front-end (which is 30 seconds), as this usually happens in about half a minute (not sure though)
,
Nov 13 2017
I can try to do that ASAP, but I'm not sure when that will be.
,
Nov 13 2017
Thank you for providing more feedback. Adding requester "kebalaji@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 13 2017
Thanks for the report, the screencast too. Unfortunately, I was unable to reproduce this. Could you please describe further what you mean by this could be "related to the timeout of the fetch request in the front-end"? Maybe kozy@ has ideas on things to try?
,
Nov 14 2017
Hi there, <FurtherDescription onSentence="related to the timeout of the fetch request in the front-end"> Sorry for the imprecise phrasing. The front-end framework I currently use, relies on XMLHttpRequest and sets XMLHttpRequest.timeout to 30000 (30 seconds) by default; i.e. the XHR is considered failed by the front-end after 30seconds. So if a XMLHttpRequest is sent, the front-end triggers the fetch event handler in the service worker, which is usually (e.g. in this screencast) often a point where I start to debug. It occurred to me that the disconnection pattern I see in the devtools could about coincide with that value. However, I am not sure if this is causally-related at all; it could just be a spurious correlation. I missed to analyze whether this might be related so far. I decided now to attempt setting the XMLHttpRequest.timeout to 0 (i.e. no timeout for the XHR) and see whether the problem will occur again. </FurtherDescription> Sorry for not producing a test case myself yet; I'm a bit stressed at work currently... ;-)
,
Nov 14 2017
Thank you for providing more feedback. Adding requester "luoe@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 16 2017
As per Comment #5,adding "Needs-Feedback" label. Thanks..
,
Nov 16 2017
Unable to triage this issue from TE-End, hence adding TE-NeedsTriageHelp label for further triage from dev team
,
Nov 27 2017
,
Dec 12 2017
Could you please try latest Chrome Canary and confirm that it is still an issue?
,
Sep 21
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by kebalaji@chromium.org
, Nov 10 2017Labels: Needs-Feedback Needs-Triage-M63