-
Bug
-
Resolution: Fixed
-
P4
-
25
-
b21
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8357412 | 21.0.9-oracle | Tejal Wakchaure | P4 | Resolved | Fixed | master |
| JDK-8357430 | 17.0.17-oracle | Tejal Wakchaure | P4 | Resolved | Fixed | master |
| JDK-8357429 | 11.0.29-oracle | Tejal Wakchaure | P4 | Resolved | Fixed | master |
| JDK-8357431 | 8u471 | Tejal Wakchaure | P4 | Resolved | Fixed | master |
nsk.share.jdi.Debugee.waitingEvent() takes a timeout argument. However, if the call to EventQueue.remove() times out and returns null, it just keep on retrying. The logic is incorrect for a null result. It should immediately return null. The retry path is only meant for filtering out other events, and it updates "timeLeft' before retrying to avoid endlessly repeating the loop.
- backported by
-
JDK-8357412 nsk.share.jdi.Debugee.waitingEvent() does not timeout properly
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/486acc06
-
Review(master)
openjdk/jdk/24839
(1 links to)