Memory leak in an underlying library about jwt HOT 4 CLOSED

sweet that is fixed in the v2.1.4 release

from jwt.

Sorry, I didn't realise issues were disabled
is it possible that the process is exiting before GC cleans up the objects?

GC seems to only clean up objects once the scope they were created in has disappeared
crystal-lang/crystal#10469

from jwt.

The issue was discovered in production and replicated in different ways. I don't believe it has got to do with crystal-lang/crystal#10469.

My fix for Crystal MongoDB driver could be found here. Scroll down to the very bottom to collection.cr. It may be tough to read the code, let me explain.

C binding inits 'reply' which is a C type and hence does not get GC-ed by Crystal automatically. If it were inside a Crystal type then we should have used Crystal's finalized to manually free memory.

The same may be happening with openssl_ext. Around line 20 we may be bypassing Crystal's GC and not freeing bio manually via LibCrypto.bio_free further down the code. Unfortunately, I have never been able to get acquainted with OpenSSL's API to dig further.

from jwt.

Great point!
I can't imagine many people are too intimately acquainted with OpenSSL's API - I'll have a dig

from jwt.