FreeBSD: Segfault after a small amount of data is inserted about qdrant

[feld]

I've seen other mentions of jemalloc in issues so it may be worth mentioning that jemalloc is the default memory allocator on FreeBSD

[timvisee]

Hi @feld. Thank you for the report!

Is there anything more you can provide us, such as the exact address on which it segfaulted? It's quite hard to find the culprit from this alone. Having a specific address in combination with truss output would at least allow us to map it to something more specific, such as memory map access.

We're always interested in finding ways to reproduce errors like this, because that'd make it a lot easier to debug and fix. But I'm assuming you're not doing anything super special here, but still, could you elaborate on what you're doing exactly in terms of Qdrant operations?

[feld]

I'm not certain how to get the exact address it segfaults on but I will continue investigating.

This was encountered when attempting to use FreeBSD to host qdrant for a search backend for Pleroma, a social media server that is compatible with Mastodon. When I run qdrant in a Linux VM it works fine.

https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4109