Updated comment for VMOutOfMemoryException001 test.

Author: plummercj

test/hotspot/jtreg/ProblemList-vthread.txt

@@ -557,13 +557,9 @@ vmTestbase/nsk/jdi/EventRequestManager/stepRequests/stepreq002/TestDescription.j
 vmTestbase/nsk/jdi/EventRequestManager/deleteEventRequests/delevtreqs002/TestDescription.java
 
 ###
-# For some reason that is not well understood, this test always times out on windows
-# when run with the vthread wrapper. It appears that the VMOutOfMemoryException is thrown
-# and caught as expected, but the test then times out waiting for the debuggee to exit. On the
-# debuggee side you see the following output, which might be related to the issue:
-#    Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Read-Poller"
-# And the Read-Poller thread is no longer around. Also the main debuggee thread seems
-# to have exited.
+# This test always times out on windows. This is due to the test forcing OOME in the
+# debuggee, which has the side affect of making the Read-Poller thread exit. Because
+# of this no vthreads can complete their reads, and the test times out as a result.
 
 vmTestbase/nsk/jdi/VMOutOfMemoryException/VMOutOfMemoryException001/VMOutOfMemoryException001.java windows-all