Closed
Bug 834144
Opened 12 years ago
Closed 12 years ago
large JSON crashes and perseerror
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 659333
People
(Reporter: sypachev_s_s, Unassigned)
Details
Attachments
(1 file)
309.41 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:19.0) Gecko/20100101 Firefox/19.0
Build ID: 20130116072953
Steps to reproduce:
I try to handle somehow rather big JSON file (5.2Mb).
Actual results:
I'm sure it is valid (I used http://www.freeformatter.com/json-validator.html to validate it, and of course I validate it on server with java StringEscapeUtils.escapeEcmaScript()).
First of all, I got parseerror. When filr is smaller nothing happens, everything is ok.
Second, when I try to use online validator, like http://jsonlint.com/, and manually input JSON data into input, FF crashes.
Third, it also crashes when I put directly into URL request address, to see response.
Fourth, some problems with long title had happened.
Comment 1•12 years ago
|
||
Please attach a testcase and/or an URL.
Flags: needinfo?(sypachev_s_s)
Keywords: testcase-wanted
Reporter | ||
Comment 2•12 years ago
|
||
Sorry for absence. There I found bug in Java library ('"\\ololo"' instead of '"\\\\ololo"' escape characters), and after that bug in jQuery in IE9 when emulate IE8 enabled.
With large JSON is duplicated bug #659333.
With any big file FF crashes. Take any large file (any, download free txt book, wiki dump etc.) and try to put it into any input. Sometimes, when it tries to send data, or to process data (like in json validators) it hangs up or crashes. Also, FF "remember" input date, so when you reload page, it also hangs. When "size" attribute defined for input, it cuts big data, otherwise not. Don't think it is a bug, because it's users' fault, or web masters' fault.
Flags: needinfo?(sypachev_s_s)
Updated•12 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Keywords: testcase-wanted
You need to log in
before you can comment on or make changes to this bug.
Description
•