mdindoffer
mdindoffer
I second this. This is the only thing preventing us to migrate from Apache Commons Codec to Guava.
This technically *is* a false positive. *But*, it still pointed out something of concern in my code. Since the returned `Future` is not intended to be `get()`-ed, any uncaught exceptions...
Obviously, micrometer crashes with jOOQ 3.16 and 3.17 as well: ```java Exception in thread "main" java.lang.AbstractMethodError: Receiver class io.micrometer.core.instrument.binder.db.MetricsDSLContext does not define or inherit an implementation of the resolved method...
You know, you could instead use jOOQ's Execution Listeners, I think that's what they are designed for - https://www.jooq.org/doc/latest/manual/sql-execution/execute-listeners/ Plus the record listeners for the UpdatableRecord API https://www.jooq.org/doc/latest/manual/sql-execution/crud-with-updatablerecords/crud-record-listener/ Intercepting only...
@OlegDokuka No, the memory is reclaimed afaict, sorry for the confusion. The problem is just the subscription. We are using a modified version of the linked gist to monitor live...
Any news regarding this?
@OlegDokuka Can you PTAL or assign someone else who's maintaining this project?
OK, I think I found the answer browsing the code at https://github.com/CodeIntelligenceTesting/jazzer/blob/cec3a817971f75595e23a729b2af81d61e0cf21c/src/main/java/com/code_intelligence/jazzer/junit/FuzzTestExecutor.java#L140 The solution is to add a system property with the name hardcoded in jazzer before executing the unit...
Ah I forgot about this. I am using Jazzer from time to time, haven't used it since October 2023 though (version 0.21.1). ~That said, my previous comment was wrong. Setting...