commit bf81547a47c46a8853092432635bfec6167a2388
author Mathieu Chartier <mathieuc@google.com> Thu Aug 13 13:02:01 2015 -0700
committer Mathieu Chartier <mathieuc@google.com> Thu Aug 13 14:27:35 2015 -0700
tree e46b95dc23586472449f87fb2c1e58f397a21907
parent 837b64974977f615dd1f0662857b97536acdb4dd

Ignore OOME in ThreadStress Daemon threads

When the runtime is shutting down we don't allow GC, this can cause
OOME in Daemon threads that are allocating. The OOME stack trace
printing can cause the test to fail.

Bug: 18577101
Change-Id: Iabbce3d75caada361dd06942f4b3be9907596091

test/004-ThreadStress/src/Main.java

diff --git a/test/004-ThreadStress/src/Main.java b/test/004-ThreadStress/src/Main.java
index 1db7cc8..7acd950 100644
--- a/test/004-ThreadStress/src/Main.java
+++ b/test/004-ThreadStress/src/Main.java
@@ -546,6 +546,9 @@
                     operation.perform();
                     i = (i + 1) % operations.length;
                 }
+            } catch (OutOfMemoryError e) {
+                // Catch OutOfMemoryErrors since these can cause the test to fail it they print
+                // the stack trace after "Finishing worker".
             } finally {
                 if (DEBUG) {
                     System.out.println("Finishing ThreadStress Daemon for " + id);