SIGSEGV in 3.2.0

Unfortunately im not able to create a minimal reproducible error or what causes this to happen but im getting a SIGSEGV running node 14 with the 3.2.0 library. Im able to grab this using the segfault-handler library but im not sure where to start looking if this is a bug in my code or the library itself.

exp_1 | PID 1 received SIGSEGV for address: 0xffffffff9c008b28
exp_1 | /rn/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x3785)[0x7f10ac0bf785]
exp_1 | /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7f10aeaf93c0]
exp_1 | /lib/x86_64-linux-gnu/libc.so.6(cfree+0x20)[0x7f10ae98f870]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(lcbvb_destroy+0x229)[0x7f1097d3b679]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(_ZN3lcb8clconfig10ConfigInfoD2Ev+0x19)[0x7f1097d74019]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(ZN12CccpProvider6updateEPKcS1+0x281)[0x7f1097d6ee21]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(_ZN3lcb8clconfig11cccp_updateEPKv10lcb_STATUSS2_mPK11lcb_host_st+0x112)[0x7f1097d6f0d2]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(+0x12d3af)[0x7f1097d903af]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(mcreq_dispatch_response+0x1d74)[0x7f1097d4bb14]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(_ZN3lcb6Server8try_readEP9lcbio_CTXP10rdb_IOROPE+0x3b5)[0x7f1097cf0105]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(+0x8f8a6)[0x7f1097cf28a6]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(+0x86127)[0x7f1097ce9127]
exp_1 | /rn/node_modules/couchbase/build/Release/couchbase_impl.node(+0x6fa42)[0x7f1097cd2a42]
exp_1 | node[0x13ac267]
exp_1 | node[0x13acc20]
exp_1 | node[0x13b3705]
exp_1 | node(uv_run+0x138)[0x13a12a8]
exp_1 | node(_ZN4node16NodeMainInstance3RunEv+0x244)[0xa659f4]
exp_1 | node(_ZN4node5StartEiPPc+0x115)[0x9f3d95]
exp_1 | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7f10ae9190b3]
exp_1 | node[0x982c9c]
exp_1 exited with code 139

Hello @ThrowsException looks like this issue ? if so you should see the fix for this in the upcoming release.