I raised this issue: https://github.com/google/allocation-instrumenter/issues/15 Hopefully it is being maintained...
On Wed, Apr 27, 2016 at 1:23 AM, Remko Popma <[email protected]> wrote: > Yes, this looks like a bug in the Google AllocationRecorder > <https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java> > : > > The NullPointerException we are seeing occurs when a shutdown hook > allocates a new object. > The instrumented bytecode still invokes the recordAllocation method. > > The AllocationRecorder also has a shutdown hook > <https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java#L49> > which sets > its instrumentation field to null. > These shutdown hook threads run at the same time, so if the > instrumentation field is set to null after the null check > <https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java#L236> > but before it is used in getObjectSize > <https://github.com/google/allocation-instrumenter/blob/master/src/main/java/com/google/monitoring/runtime/instrumentation/AllocationRecorder.java#L192>, > we get the exception. > > > On Wed, Apr 27, 2016 at 12:29 AM, Ralph Goers <[email protected]> > wrote: > >> Any idea how to determine what caused this to fail? >> >> Ralph >> >> > On Apr 26, 2016, at 8:07 AM, Apache Jenkins Server < >> [email protected]> wrote: >> > >> > See <https://builds.apache.org/job/Log4j%202.x/1909/changes> >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
