Provide some diagnostics with "failed to parse SourceMap" warning
Reported by
earshi...@gmail.com,
Mar 20 2018
|
|||
Issue descriptionUserAgent: 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:
,
Mar 21 2018
,
Mar 23 2018
Andrey, could you confirm #2? |
|||
►
Sign in to add a comment |
|||
Comment 1 by susan.boorgula@chromium.org
, Mar 20 2018