Looks like there is no any syncronisation is it possible that this
erroneous situation will occur after the check "canUndoOrRedo" but
before the "undoOrRedo"?
On 22/12/15 16:47, Semyon Sadetsky wrote:
Hello,
Please review fix for JDK9:
bug: https://bugs.openjdk.java.net/browse/JDK-8145787
webrev: http://cr.openjdk.java.net/~ssadetsky/8145787/webrev.00/
This is a multithreading stress test in which the undo queue depth may
reach zero sometimes occasionally. The corresponding checks were added.
--Semyon
--
Best regards, Sergey.
