Some JSON fails to parse in 64-bit Chrome
Reported by
changing...@gmail.com,
Apr 11 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. Open default.html from the attached zip file 2. From the on page chose file button open data.json from the zip file What is the expected behavior? The page should parse the JSON file and display alert saying parsed What went wrong? Parsing the JSON fails and displays the alert Parse Failed and the error message RangeError: Maximum call stack size exceeded Did this work before? No Chrome version: 57.0.2987.133 Channel: stable OS Version: 10.0 Flash Version: This works for 64 and 32 bit versions of IE and Firefox, Edge and Chrome 32-bit on Windows. It only fails on 64-bit Chrome. I have other JSON files, both larger and smaller that parse fine and others also larger and smaller that also fail so it seems like a specific character or sequence that causes the issue
,
Apr 12 2017
Chrome-TE, please bisect. Did this work with Chrome 56?
,
Apr 13 2017
,
Apr 13 2017
Tested the issue on chrome Stable #57.0.2987.133 and Canary 59.0.3069.0 in Windows 10.0 & 7 and was able to reproduce the issue. This is a Non-Regression issue since seeing this from M30 #30.0.1549.0,Status is in available so not changing the status so that the issue would get addressed. Note : Able to reproduce the issue in MAC 10.12 and Linux Ubuntu 14.04. Thank you.
,
Apr 4 2018
This has been a year now Is there any idea when this might be fixed?
,
Apr 4 2018
I don't think we have plans to fix this. The JSON parser recurses. This particular JSON string is simply too deeply nested. We could of course implement some sort of deferring to parse in case of stack overflow. But I'm not convinced this is a good use of our energy right now. Patches welcome though.
,
Apr 10 2018
How can the JSON be too deeply nested when it works in every other browser and 32 bit Chrome? This is obviously just a bug with the 64bit version parsing valid JSON This issue is causing us problems with our app/site for cilents who are mostly using 64bit Chrome. Please can you fix this |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by junov@chromium.org
, Apr 11 2017