Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
P3
-
Resolution: Fixed
-
Affects Version/s: 9
-
Fix Version/s: 9
-
Component/s: client-libs
-
Subcomponent:
-
Resolved In Build:b124
-
CPU:generic
-
OS:generic
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8248244 | openjdk8u272 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
JDK-8247300 | 8u271 | Sergey Bylokhov | P3 | Resolved | Fixed | b01 |
JDK-8251708 | emb-8u271 | Sergey Bylokhov | P3 | Resolved | Fixed | team |
Description
I just found one of the reason why some of our tests hangs. Example of the test:
closed/javax/sound/sampled/Clip/bug5070081.java
The problem is that the tests uses this pattern:
clip.start();
while(clip.isRunning());
The status running or not is updated on a different thread, but our clip implementations lack of synchronization of getters and the hotspot inline such methods to while(true).
closed/javax/sound/sampled/Clip/bug5070081.java
The problem is that the tests uses this pattern:
clip.start();
while(clip.isRunning());
The status running or not is updated on a different thread, but our clip implementations lack of synchronization of getters and the hotspot inline such methods to while(true).
Attachments
Issue Links
- backported by
-
JDK-8247300 Some sound tests rarely hangs because of incorrect synchronization
-
- Resolved
-
-
JDK-8248244 Some sound tests rarely hangs because of incorrect synchronization
-
- Resolved
-
-
JDK-8251708 Some sound tests rarely hangs because of incorrect synchronization
-
- Resolved
-