The new regression test java.util.logging.TestMemoryHandler.java
creates 4 billion objects. It's no surprise this takes a long time,
and times out on sufficiently slow machines. This test causes
a regression failure on our solaris-sparc autobuild machines.

Also, 10 minutes is an unreasonable running time for a test that
tests so little.

One way to fix the test failure and speed up the test is to restrict
the max memory usage explicitly via, for example,

 * @run main/othervm -Xms3m -Xmx3m TestMemoryHandler

and then using the lowest iteration count that fails pre-fix
and succeeds post-fix.

My apologies for not having caught this before the b17 integration.
###@###.### 2004-12-18 22:01:22 GMT