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

Issue 671038 link

Starred by 2 users
Status: Fixed
Owner:
█ kozyatinskiy@chromium.org
Last visit > 30 days ago
Closed: Jun 2017
Cc:
█ lushnikov@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

scope.startLocation is inconsistent, causes trouble in Sources.SourceMapNamesResolver.resolveScopeInObject

Reported by antonin....@gmail.com, Dec 4 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2939.0 Safari/537.36

Steps to reproduce the problem:
Started seeing "TypeError: Cannot read property 'sourceMapURL' of null" errors.

What is the expected behavior?

What went wrong?
startLocation.script() returns null, because internal scriptId is "2", but debugger model is somehow out-of-sync and tracks only scripts with IDs #27 - #259.

https://github.com/binaryage/dirac/blob/2eee2aae209e78a3113acefad5d8f0d79f9734b8/front_end/sources/SourceMapNamesResolver.js#L345

https://dl.dropboxusercontent.com/u/559047/resolve-scope-in-object-issue-01.png

Did this work before? N/A 

Chrome version: 57.0.2939.0  Channel: canary
OS Version: OS X 10.12.1
Flash Version: Shockwave Flash 24.0 r0

Comment 1 by antonin....@gmail.com, Dec 4 2016 

This bug might be caused interaction with Dirac. I just wanted to point out that resolveScopeInObject should maybe be more robust and test startLocation.script() to be non-null. Or there should be some checks earlier to prevent location object inconsistency.

Comment 2 by hdodda@chromium.org, Dec 5 2016

Labels: TE-NeedsTriageHelp

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

Labels: M-57

Comment 4 by paulir...@chromium.org, Dec 14 2016

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

Comment 5 by kozyatinskiy@chromium.org, Jun 6 2017

Status: Fixed (was: Assigned)
Check for startLocation.script() was added.
►

Sign in to add a comment