The test vm/oom/production/OOMProductionAnonymousTrace_Arrays (vmtestbase) is filling the heap until it gets an OOME. In the latest GC nightly the test threw an exception saying that the stack trace it created when throwing the exception was corrupt:

[2015-01-07T05:50:49.51] nsk.share.TestFailure: Expected element at index 5 to match: at ?.create(?:0)
[2015-01-07T05:50:49.51] at vm.share.stack.StackUtils.checkMatches(StackUtils.java:73)
[2015-01-07T05:50:49.51] at vm.oom.OOMTraceTest.checkExpectedTraceElements(OOMTraceTest.java:40)
[2015-01-07T05:50:49.51] at vm.oom.OOMTraceTest.checkOOM(OOMTraceTest.java:63)
[2015-01-07T05:50:49.51] at vm.oom.OOMTraceTest.run1(OOMTraceTest.java:88)
[2015-01-07T05:50:49.51] at vm.oom.OOMTraceTest.run(OOMTraceTest.java:99)
[2015-01-07T05:50:49.51] at nsk.share.test.Tests$TestRunner.execute(Tests.java:63)
[2015-01-07T05:50:49.51] at nsk.share.test.Tests$TestRunner.run(Tests.java:77)
[2015-01-07T05:50:49.51] at nsk.share.gc.GC.runTest(GC.java:95)
[2015-01-07T05:50:49.51] at vm.oom.production.OOMProductionAnonymousTraceTest.main(OOMProductionAnonymousTraceTest.java:56)

Looking at the history of this test this has happened twice before.

I suspect it may be a test issue since there might not be enough memory left to create the stack trace when the heap has been deliberately filled to its limit.