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

Issue 673675 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug

Blocked on:
issue 570298



Sign in to add a comment

No initiator URL in chrome.debugger for some requests

Reported by anna.lar...@gmail.com, Dec 13 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36

Steps to reproduce the problem:
1. Install  slightly changed chrome plugin from https://github.com/anna-lareni/chrome-extension-http-headers. I only changed a few lines https://github.com/anna-lareni/chrome-extension-http-headers/commit/9542c2d9d59ea5217b607600a9b338dc5334395b
2. Open http://moerner.com/tests/chrome-debug-api/
3. Start the plugin via the green button top right
4. Reload the website via shift + reload

What is the expected behavior?
An initiator for every request incl URL should be shown.

What went wrong?
http://moerner.com/tests/chrome-debug-api/ -> {"type":"other"}
http://b.aklamio.com/widget-integration.js?1481620862017 -> {"stack":{"callFrames":[{"columnNumber":31,"functionName":"","lineNumber":10,"scriptId":"44","url":"http://moerner.com/tests/chrome-debug-api/"},{"columnNumber":11,"functionName":"","lineNumber":11,"scriptId":"44","url":"http://moerner.com/tests/chrome-debug-api/"}]},"type":"script"}
https://www.aklamio.com/ovlbtntrk?url=http%3A%2F%2Fmoerner.com%2Ftests%2Fchrome-debug-api%2F&utm_medium=blank&r= -> {"stack":{"callFrames":[]},"type":"script"}

As you see in line 3, the callFrames array is empty. 

On the other hand if I use the developer tools an initiator-URL is shown (see screenshot)

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 51.0.2704.84  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 24.0 r0
 
chrome-dev-tools.jpg
49.0 KB View Download
Hi,

I made a few tests more on this: 55.0.2883.87 seems to have the same issue.

Surprisingly sometimes the callFrames array is *not* empty. After a couple of reloads and/or Chrome restarts the callFrames array is empty again. 

The callFrames response looks very flappy to me or do I miss something here? Is there a trick to make this stable?

Thanks,
Anna

By the way. I tested this with Linux as well. Same behavior.

Comment 3 by ajha@chromium.org, Dec 15 2016

Labels: M-55 prestable-55.0.2883.87 OS-Linux
Components: Platform>DevTools
Labels: TE-NeedsTriageHelp

Comment 5 by allada@chromium.org, Jan 10 2017

Blockedon: 570298
Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 6 by allada@chromium.org, Jan 10 2017

Labels: -TE-NeedsTriageHelp
Status: Archived (was: Assigned)

Sign in to add a comment