-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 7
-
Component/s: core-svc
-
b32
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2166391 | 6u10 | James Holmlund | P3 | Resolved | Fixed | b31 |
| JDK-2185798 | OpenJDK6 | Kelly Ohair | P3 | Resolved | Fixed | b18 |
The spec says they are invalidated because the info contained in the MonitorInfo object might no longer be correct after a resume occurs.
For example, the stack depth might be different, and the monitor might not even be owned by the thread anymore.
This bug is covered by the following new JTREG test:
com/sun/jdi/MonitorFrameInfo.java
For example, the stack depth might be different, and the monitor might not even be owned by the thread anymore.
This bug is covered by the following new JTREG test:
com/sun/jdi/MonitorFrameInfo.java
- backported by
-
JDK-2166391 MonitorInfo objects aren't invalidated when the owning thread is resumed
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Closed
-
-
-
- Closed
-