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

Issue 689896 link

Starred by 4 users
Status: Assigned
Owner:
kozy@chromium.org
Cc:
█ kavvaru@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
TC


Sign in to add a comment

Can not get "Debugger.paused" event when debugger is called from a page from extension folder

Reported by findwa...@126.com, Feb 8 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.67 Safari/537.36

Steps to reproduce the problem:
1. Launch Chrome
2. Load the unpacked extension from the attachment(DebuggerFreeze.7z), "Extension UI" page will be opened after the extension is loaded.  
3. Click "Click me to open a page from extension folder" button to open a page from extension folder.
4. After a few seconds, the "Extension UI" page will freeze, the timer on this page will not be refreshed.

Here are what the logic of extension attached.
A page will be opened when button is clicked in "Extension UI" page.
The content script will send "hello" message to background page and call "debugger" statement to pause code execution. 
Background page will attach to opened tab and listen on debugger event, "Debugger.paused" event is the only interested event. Code execution of the source page will be resumed if "Debugger.paused" event is received.
In general, page will paused itself and background page will resume it.
The issue is "Debugger.paused" event will not be received if the "debugger" statement is called from a page from extension. "Debugger.paused" event can be received if the "debugger" statement is called from a page outside extension, for example, http://www.google.com.
You can play with the buttons in "Extension UI" page to see the difference.

What is the expected behavior?
"Debugger.pause" event should be received when the "debugger" statement is called from both pages inside extension and outside extension.

What went wrong?
The issue is "Debugger.paused" event will not be received if the "debugger" statement is called from a page from extension. 
This issue can only be reproduced on Chrome 56. I tested 55, 54, 53, it works as expected. It looks like a defect introduced in 56.

Did this work before? Yes 55

Chrome version: 56.0.2924.67  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
DebuggerFreeze.7z
10.7 KB Download

Comment 1 by ligim...@chromium.org, Feb 8 2017

Labels: Pri-1
****Bulk Edit****

Setting as P1 for test team to prioritize in triaging.

Comment 2 by kozyatinskiy@chromium.org, Feb 9 2017

Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by kavvaru@chromium.org, Feb 9 2017

Cc: kavvaru@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on windows 7, Linux Ubuntu 14.04 using chrome version 56.0.2924.87 with the below steps

1.Load the attached extension 
2.Clicked on First button
3.Clicked on "Click me to open a page from extension folder" button
4.Not observed any freezing behavior

Please find the attached screen cast and confirm if anything missed here.
Request you please try the issue on new profile and update the thread if the issue still persists.

Thanks,
689896.mp4
993 KB View Download

Comment 4 by findwa...@126.com, Feb 9 2017 

It seems that PageInsideExtension.html is closed after the second button is clicked. This page should remain open to see the freeze issue. Please don't close it when switch to the "Extension UI" page. The timer will stop updating after about 3 seconds(3 seconds delay to make sure debugger is attached to the opened tab).

Comment 5 by findwa...@126.com, Feb 10 2017 

I tested on Chrome 57 and encounter the same issue. Please refer to the attached video for detail. Hopefully it will help you understand what the issue is.
Chrome57.wmv
482 KB Download

Comment 6 by kozyatinskiy@chromium.org, Oct 16 2017

Owner: kozy@chromium.org
►

Sign in to add a comment