-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 8u20, 9
-
Component/s: core-libs
-
None
-
b02
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8045060 | 8u25 | Sundararajan Athijegannathan | P2 | Resolved | Fixed | b01 |
| JDK-8037977 | 8u20 | Sundararajan Athijegannathan | P2 | Closed | Fixed | b09 |
| JDK-8052460 | emb-8u26 | Sundararajan Athijegannathan | P2 | Resolved | Fixed | b18 |
Hard to reproduce and reduce...
The pasted testcase gets you the scopeCall with -1 as line number. As soon as one of the fn declaration is commented, scopeCall vanishes.
It is observed in avatar-js dumped stacks.
function fail() {
throw new Error("Strange...");
}
var f2 = fail;
var f3 = fail;
var f4 = fail;
var f5 = fail;
try {
fail();
}catch(err) {
print(err.stack);
}
The pasted testcase gets you the scopeCall with -1 as line number. As soon as one of the fn declaration is commented, scopeCall vanishes.
It is observed in avatar-js dumped stacks.
function fail() {
throw new Error("Strange...");
}
var f2 = fail;
var f3 = fail;
var f4 = fail;
var f5 = fail;
try {
fail();
}catch(err) {
print(err.stack);
}
- backported by
-
JDK-8045060 scopeCall with -1 as line number
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-