Leaking okhttp3.OkHttpClient connections

[kingslef]

Occasionally (quite rarely) I'm seeing the following log:

okhttp3.OkHttpClient - A connection to https://ingest.lightstep.com/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);

I'm using lightstep-tracer-jre version 0.30.1 and GRPC.

---

I'm not setting the URL anywhere in my application, so by the looks of it, it must be the default metrics URL. I haven't been able to reproduce it easily, but looking at the code, I noticed this. It looks like the the response.body is never closed, even though instructed by OkHttp (see e.g. square/okhttp#2311). It is definitely not closed if the response is not 200, but also the parseFrom seems to leave it open.

Or am I missing something?

[kingslef]

These disappeared after upgrading 0.30.3. Thanks!