-
Bug
-
Resolution: Fixed
-
P3
-
21, 22
-
b12
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8334409 | 21.0.5-oracle | Harshitha Onkar | P3 | Resolved | Fixed | b01 |
JDK-8334583 | 21.0.5 | Martin Doerr | P3 | Resolved | Fixed | b01 |
JDK-8335639 | 17.0.13-oracle | Harshitha Onkar | P3 | Resolved | Fixed | b02 |
JDK-8336721 | 17.0.13 | Matthias Baesken | P3 | Resolved | Fixed | b01 |
JDK-8337952 | 11.0.26-oracle | Harshitha Onkar | P3 | Resolved | Fixed | b01 |
JDK-8340569 | 8u441 | Renjith Kannath Pariyangad | P3 | Resolved | Fixed | b01 |
e.g.
for (int i = 0; i < 50; i++) {
for (int j = 0; j < 50; j++) {
robot.getPixelColor(i, j);
}
}
While this is not the most efficient way to get data from the screen (you can use createScreenCapture), it can be sped up.
Currently we create a screencast session from scratch for each call to getPixelColor or createScreenCapture.
To speed it up, we can close the session after some reasonable time (2s for example) if there is no new screen capture attempt.
We should also change the tests to use createScreenCapture in such cases.
- backported by
-
JDK-8334409 [XWayland][Screencast] consequent getPixelColor calls are slow
- Resolved
-
JDK-8334583 [XWayland][Screencast] consequent getPixelColor calls are slow
- Resolved
-
JDK-8335639 [XWayland][Screencast] consequent getPixelColor calls are slow
- Resolved
-
JDK-8336721 [XWayland][Screencast] consequent getPixelColor calls are slow
- Resolved
-
JDK-8337952 [XWayland][Screencast] consequent getPixelColor calls are slow
- Resolved
-
JDK-8340569 [XWayland][Screencast] consequent getPixelColor calls are slow
- Resolved
- links to
-
Commit openjdk/jdk21u-dev/2e8418e3
-
Commit openjdk/jdk/2f04bc5f
-
Commit(master) openjdk/jdk17u-dev/07be2e55
-
Review openjdk/jdk21u-dev/743
-
Review openjdk/jdk/15250
-
Review(master) openjdk/jdk17u-dev/2717