JDK-8137281 : OutOfMemoryError with large numeric keys in JSON.parse
- Type: Bug
- Component: core-libs
- Sub-Component: jdk.nashorn
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2015-09-28
- Updated: 2016-01-14
- Resolved: 2015-10-02
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 | JDK 9 |
|---|---|
8u72Fixed  |
9 b85Fixed |
Description
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.