-
Bug
-
Resolution: Fixed
-
P3
-
8u40
-
b10
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8059940 | 9 | Hannes Wallnoefer | P3 | Resolved | Fixed | b35 |
| JDK-8085742 | emb-9 | Hannes Wallnoefer | P3 | Resolved | Fixed | team |
| JDK-8064242 | 8u45 | Hannes Wallnoefer | P3 | Resolved | Fixed | b01 |
| JDK-8070479 | emb-8u47 | Hannes Wallnoefer | P3 | Resolved | Fixed | team |
Running octane pdfjs with optimistic typing it is visible how occupied OldSpace is increasing in time. It causes performance degradation and OutOfMemoryError at the end.
Used heap increases slowly - required long execution: e.g. with 512M heapsize it requires up to 200-300 iterations before OOM:
java -Xmx512m -Xms512m jdk.nashorn.tools.Shell test/script/basic/run-octane.js --optimistic-types=true -scripting -- pdfjs --runtime nashorn --verbose --iterations 300
PS There is no memory leak when optimistic typing turned off.
Used heap increases slowly - required long execution: e.g. with 512M heapsize it requires up to 200-300 iterations before OOM:
java -Xmx512m -Xms512m jdk.nashorn.tools.Shell test/script/basic/run-octane.js --optimistic-types=true -scripting -- pdfjs --runtime nashorn --verbose --iterations 300
PS There is no memory leak when optimistic typing turned off.
- backported by
-
JDK-8059940 Memory leak when executing octane pdfjs with optimistic typing
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-