Setting breakpoint in Port.onDisconnect in a content script causes entire browser to deadlock
Reported by
k...@luminance.org,
Mar 8 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 Steps to reproduce the problem: 1. Inject a content script into a page from your extension's background page 2. Content script opens a port to the background page and registers an onDisconnect handler 3. Set a breakpoint in the onDisconnect handler 4. Reload extension background page What is the expected behavior? Content script should get onDisconnect event and page should continue working after you resume from the breakpoint What went wrong? Entire browser deadlocks after you resume from the breakpoint. Pausing again shows that the browser is firing onDisconnect events over and over (through dispatchOnDisconnect in extensions::messaging) and each fire causes an exception in getPrivateImpl. The tab cannot be closed and 'Exit' does not work. WebStore page: Did this work before? N/A Chrome version: Version 64.0.3282.186 (Official Build) (64-bit) Channel: stable OS Version: 10.0 Flash Version:
,
Mar 8 2018
kg@ Thanks for the issue. Request you to provide a sample extension and a screen cast of the steps followed to reproduce the issue, which will help in further triaging. Thanks.
,
Mar 8 2018
What should I use to provide a screen cast?
,
Mar 8 2018
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
,
Mar 9 2018
,
Mar 12 2018
@Reporter: Without a sample extension file it will not be possible triage this issue. Please provide for further investigation on this. In response to comment#3, please use Screencast o matic from here https://screencast-o-matic.com/ to record a video. Thanks!
,
Jun 1 2018
As there is no response from the reporter from so long, closing this issue as Won't fix. @Reporter: Please feel to raise a new issue if issue is still seen. Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by k...@luminance.org
, Mar 8 2018