Issue metadata
Sign in to add a comment
|
breakpoints not hit in chrome extension background page
Reported by
efo...@gmail.com,
Dec 9
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: download any plugin, set a breakpoint on background.js from the chrome extensions background page and its never hit. What is the expected behavior? should pause at breakpoint What went wrong? new version of chrome broke debugging, worked before. Did this work before? Yes not sure Chrome version: 70.0.3538.110 Channel: n/a OS Version: 10.0 Flash Version:
,
Dec 10
eformx@ Thanks for the issue. Request you to provide a sample extension where this issue can be reproduced, which will help in further triaging. Also a screencast of the steps followed and the issue observed will help in better understanding of the issue. Thanks..
,
Dec 10
I open an extension background page (F12 Console extension) from chrome/extensions, put a break point in any of the background javascript files (that are listed in the manifest) and the breakpoints are never hit. Doesn't matter who's plugin I try this with, breakpoints are not hit (Version 70.0.3538.110 (Official Build) (64-bit)). The only way I can hit a breakpoint is if I introduce an error in the script, the debugger stops and then I can hit a breakpoint from vm pages that show up. So it hits the vm pages but not the background page from chrome/extensions. Perhaps you have changed how to hit a breakpoint? Do you have a published web page that outlines how you are supposed to hit or mark a breakpoint before the page is loaded? Then I can retest with those instructions as a baseline. Screenshot of my test setup attached. Thanks.
,
Dec 10
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
,
Dec 11
,
Dec 11
eformx@ Thanks for the update. Tested this issue on Windows 10 on the reported version 70.0.3538.110 and the latest Canary 73.0.3637.0 by following the below steps. 1. Launched Chrome and added an Extension in chrome://extensions. 2. Clicked on the background page and opened a .js file. 3. Set a breakpoint and hit F5. Attached is the screen cast for reference. Request you to check and confirm if anything is missed from our end in triaging the issue. Also request you to provide a screen cast of the steps followed which will help in further triaging of the issue. Thanks..
,
Dec 11
In your video the breakpoint can be set; but it does not stop at the breakpoint and highlight the line (should be light blue highlight at breakpoiint). Then navigate over a variable to show that it has been set. It does not work. The pause at the breakpoint does not occur, and that is on various machines.
,
Dec 11
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
,
Dec 11
I can reliably break in the background script. Setting a breakpoint, hitting F5 and it stops right away. Could you try this with the clean profile?
,
Dec 12
clean profile? you mean a different google account?
,
Dec 12
eformx@ For a clear profile, request you to follow the below steps. 1. Click on the Person icon on the top right corner of the window. 2. Click on manage people -> Add person. Request you to retry the issue in a new person and update the thread with the observations. Thanks..
,
Jan 7
Can't repro.
,
Jan 7
Made no difference. 1. Click on the Person icon on the top right corner of the window.2. Click on manage people -> Add person. Then dropped folder of extension onto chrome extensions window for newly added person. Select background page from extensions window. Open source of extension, have 4 background pages (diff names of course). Set break point for login click event. Login to plugin and works perfectly; however break point at click event entry point not hit. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Dec 9