Guess we have to fork it? Ralph
> On May 3, 2016, at 11:48 AM, Gary Gregory <[email protected]> wrote: > > Yikes, no reply on > https://github.com/google/allocation-instrumenter/issues/15 > <https://github.com/google/allocation-instrumenter/issues/15> > > G > > On Thu, Apr 28, 2016 at 10:51 AM, Remko Popma <[email protected] > <mailto:[email protected]>> wrote: > Hi Colin, > > I'm contacting you because you are listed as one of the contributors to the > allocation-instrumenter <https://github.com/google/allocation-instrumenter> > project on GitHub. > > We are working on Log4j 2 <http://logging.apache.org/log4j/2.x/>, and the > main theme of the upcoming 2.6 release is making Log4j 2 garbage-free > <https://issues.apache.org/jira/browse/LOG4J2-1270> in steady state running. > We use the allocation instrumenter in our JUnit tests to verify that things > are working as expected. > > However, on our build server we see our test fail spuriously. > I believe this is a bug in AllocationRecorder (to do with accessing a > volatile field that has been nulled out by a shutdown hook, details here > <https://github.com/google/allocation-instrumenter/issues/15>). > > Could you please take a look? > If you no longer maintain this project, can you point us to the person who > does? > > Many thanks! > Remko Popma > > > > > > -- > E-Mail: [email protected] <mailto:[email protected]> | > [email protected] <mailto:[email protected]> > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com <http://garygregory.wordpress.com/> > Home: http://garygregory.com/ <http://garygregory.com/> > Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
