* mark harwood:
> Thanks, I have a heap dump now from a run with reduced JVM memory
> (in order to speed up a failure point) and am working through it
> offline with VisualVm.
> This test induced a proper OOM as opposed to one of those "timed out
> waiting for GC " type OOMs so may be misleading.
* mark harwood:
>>>Could you get a heap dump (eg with YourKit) of what's using up all the
>>>memory when you hit OOM?
>
> On this particular machine I have a JRE, no admin rights and
> therefore limited profiling capability :(
Maybe this could give you a heap dump which you can analyze on a
diff
