-
Bug
-
Resolution: Fixed
-
P3
-
6
-
b17
-
x86
-
windows_xp
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2150762 | 6u10 | Vikram Aroskar | P3 | Resolved | Fixed | b12 |
J2SE Version (please include all output from java -version flag):
java version "1.6.0-rc"
Java(TM) SE Runtime Environment (build 1.6.0-rc-b91)
Java HotSpot(TM) Client VM (build 1.6.0-rc-b91, mixed mode, sharing)
Does this problem occur on J2SE 1.4.x or 5.0.x ? Yes / No (pick one)
not known
Operating System Configuration Information (be specific):
Windows XP Professional SP2
Hardware Configuration Information (be specific):
Intel Pentium III, 730 Mhz, 384 Mb RAM
Bug Description:
A mouse listener method happens to process mouse events whose time
is in the future.
Steps to Reproduce (be specific):
Compile and run the attached program. A window is displayed.
Move the mouse in it. On the command prompt window mouse events
are traced. Some of them report "delay = -1". This is the
difference between the current time and the time of the event.
A negative number means that the event has in it a time in the
future. However coarse might the system clock be, it should never
go back. Therefore, if the system clock is consistently used
all over JRE, an event occurring before another can never have
a timestamp greater that that of the other.
java version "1.6.0-rc"
Java(TM) SE Runtime Environment (build 1.6.0-rc-b91)
Java HotSpot(TM) Client VM (build 1.6.0-rc-b91, mixed mode, sharing)
Does this problem occur on J2SE 1.4.x or 5.0.x ? Yes / No (pick one)
not known
Operating System Configuration Information (be specific):
Windows XP Professional SP2
Hardware Configuration Information (be specific):
Intel Pentium III, 730 Mhz, 384 Mb RAM
Bug Description:
A mouse listener method happens to process mouse events whose time
is in the future.
Steps to Reproduce (be specific):
Compile and run the attached program. A window is displayed.
Move the mouse in it. On the command prompt window mouse events
are traced. Some of them report "delay = -1". This is the
difference between the current time and the time of the event.
A negative number means that the event has in it a time in the
future. However coarse might the system clock be, it should never
go back. Therefore, if the system clock is consistently used
all over JRE, an event occurring before another can never have
a timestamp greater that that of the other.
- backported by
-
JDK-2150762 A mouse listener method happens to process mouse events whose time is in the future.
- Resolved
- relates to
-
JDK-8046495 KeyEvent can not be accepted in quick mouse clicking
- Resolved
-
JDK-6207371 InputEvent.getWhen() (and similar) does not specify timebase of timestamp
- Resolved
-
JDK-6626492 Event time in future part 2, now on X
- Resolved
-
JDK-4511903 At times getWhen()in ActionEvent returns higher value than the CurrentSystemTime
- Closed
-
JDK-6461933 To adjust system boot time in nowMillisUTC() frequently
- Closed
(1 relates to)