New issue
Advanced search Search tips

Issue 778899 link

Starred by 1 user
Status: Fixed
Owner:
kozy@chromium.org
Closed: Sep 25
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Unrelated error being thrown when inspecting window.parent variable in debugger

Reported by randin...@gmail.com, Oct 27 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36

Steps to reproduce the problem:
1. Open dev tool.
2. Go to http://upbeat-oatmeal.surge.sh/
3. Hover the mouse on the "parent" variable in "window.parent".

What is the expected behavior?
No error in the console log.

What went wrong?
A bunch unrelated errors will be thrown in the console log.

Did this work before? No 

Chrome version: 62.0.3202.75  Channel: stable
OS Version: OS X 10.13.0
Flash Version: 

This issue will cause "Aw, snap" in the previous version of Chome.
It seems much better now but throwing these errors is still not the desired behavior.

Comment 1 by susanjuniab@chromium.org, Oct 27 2017

Cc: susanjuniab@chromium.org
Labels: -Type-Bug -Pri-2 hasbisect-per-revision M-64 Needs-Triage-M62 OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: verwa...@chromium.org
Status: Assigned (was: Unconfirmed)
randing89@ Thanks for the issue

Able to reproduce this issue on Windows 7, Mac 10.12.6 and Ubuntu 14.04 with Chrome Stable 62.0.3202.75 and Canary 64.0.3251.0.

Below is the Bisect Information.

Bisect Information:
=====================
Good Build 61.0.3118.0 Revision-476500
Bad Build  61.0.3119.0 Revision-476838

Note: Till 61.0.3118.0 build, crash on the page is observed by following the steps mentioned in the original comment.
From 61.0.3119.0 build, can see the error on the Console by following the steps.
Hence considering 61.0.3118.0 as the good build and 61.0.3119.0 as the bad build.

Below is the change log using the per-revision bisect script.

CHANGELOG URL:
===============
https://chromium.googlesource.com/chromium/src/+log/c8c17ea5f62b4d647f2cb4e892333927d8e37779..e7d2b30b9a2b6e04a67cefb219fc4e5af122b8a2

From the above change log suspecting below change
 https://chromium-review.googlesource.com/522605

verwaest@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks.!

Comment 2 by verwa...@chromium.org, Oct 30 2017

Cc: -susanjuniab@chromium.org
Owner: susanjuniab@chromium.org
Some piece of code associated with DevTools is accessing the "naked global object" (instead of the global proxy). Previously it was crashing when trying to read the "history" property since it didn't support the global object as receiver (The global object should never leak into JS code...).

My CL changes it to now swap the global object for the global proxy. That makes the history getter work, but something in the extension/module-system is failing afterwards. I suppose this has never worked in this cross-origin setting...

I don't think there's anything for me to do here.

Comment 3 by pfeldman@chromium.org, Dec 14 2017

Owner: kozy@chromium.org

Comment 4 by kozy@chromium.org, Sep 25

Status: Fixed (was: Assigned)
This one is fixed in latest Google Chrome Canary.
►

Sign in to add a comment