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

Issue 823645 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit 28 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Provide some diagnostics with "failed to parse SourceMap" warning

Reported by earshi...@gmail.com, Mar 20 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36

Steps to reproduce the problem:
I regularly get this warning:

DevTools failed to parse SourceMap: <URL to sourcemap>

With a large production build it is a formidable challenge to identify the cause of the problem.

What is the expected behavior?
It would be very helpful to have some additional diagnostics like
  - the location within the sourcemap causing the problem
  - the root of the problem (Couldn't Chromium parse the file due to an incorrect encoding or invalid symbols?  Are mappings within the sourcemap incorrect and do not properly map to sourcesContent? etc.)

What went wrong?
At the moment the warning does not contain any information which may be used to resolve the issue with the sourcemap.

Did this work before? N/A 

Chrome version: 65.0.3325.146  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 
Labels: Needs-Triage-M65
Cc: lushnikov@chromium.org viswa.karala@chromium.org
Labels: Triaged-ET
@lushnikov: Could you please confirm whether this issue is similar to that of issue:  796368 ,  794965 .

Thanks!
Owner: kozy@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 4 by kozy@chromium.org, Mar 23 2018

Owner: lushnikov@chromium.org
Andrey, could you confirm #2?

Sign in to add a comment