-
Bug
-
Resolution: Fixed
-
P4
-
8
-
b09
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8037231 | 9 | Hannes Wallnoefer | P4 | Resolved | Fixed | b06 |
| JDK-8045079 | 8u25 | Hannes Wallnoefer | P4 | Resolved | Fixed | b01 |
| JDK-8052479 | emb-8u26 | Hannes Wallnoefer | P4 | Resolved | Fixed | b18 |
Reported by Walter Higgins on nashorn-dev:
http://mail.openjdk.java.net/pipermail/nashorn-dev/2014-February/002745.html
The problem is that the global variable is configurable but callsites using it will not be properly guarded.
Script to reproduce:
global = this;
function test() {
global.self = 123;
try {
print(self);
} finally {
delete global.self;
}
}
test();
test();
test();
http://mail.openjdk.java.net/pipermail/nashorn-dev/2014-February/002745.html
The problem is that the global variable is configurable but callsites using it will not be properly guarded.
Script to reproduce:
global = this;
function test() {
global.self = 123;
try {
print(self);
} finally {
delete global.self;
}
}
test();
test();
test();
- backported by
-
JDK-8037231 delete on global object not properly guarded
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8035950 Add guards for callsites depending on global object
-
- Resolved
-