-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b85
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8142300 | emb-9 | Hannes Wallnoefer | P3 | Resolved | Fixed | team |
JDK-8141009 | 8u91 | Hannes Wallnoefer | P3 | Resolved | Fixed | b01 |
JDK-8138818 | 8u72 | Hannes Wallnoefer | P3 | Resolved | Fixed | b01 |
JDK-8147378 | emb-8u91 | Hannes Wallnoefer | P3 | Resolved | Fixed | b01 |
Parsing JSON with lots of large numeric keys can throw an OOM.
http://stackoverflow.com/questions/32787100/nashorn-json-parse-java-lang-outofmemoryerror-java-heap-space-jdk8u60
The problem is that we don' switch to sparse array data soon enough. The current threshold (defined in SparseArrayData.MAX_DENSE_LENGTH) is 8 * 1024 * 1024.
http://stackoverflow.com/questions/32787100/nashorn-json-parse-java-lang-outofmemoryerror-java-heap-space-jdk8u60
The problem is that we don' switch to sparse array data soon enough. The current threshold (defined in SparseArrayData.MAX_DENSE_LENGTH) is 8 * 1024 * 1024.
- backported by
-
JDK-8138818 OutOfMemoryError with large numeric keys in JSON.parse
-
- Resolved
-
-
JDK-8141009 OutOfMemoryError with large numeric keys in JSON.parse
-
- Resolved
-
-
JDK-8142300 OutOfMemoryError with large numeric keys in JSON.parse
-
- Resolved
-
-
JDK-8147378 OutOfMemoryError with large numeric keys in JSON.parse
-
- Resolved
-