Open gburd opened 12 years ago
What I observe is that when snappy is being used, the ebloom NIFs start reporting badarg! Looks like the nif_resource representing an ebloom is suddenly not valid. So it smells like snappy is corrupting memory outside its own objects.
Although Snappy compression has been integrated sometimes compression fails in the snappy erlang integration libraries we use (https://github.com/fdmanana/snappy-erlang-nif).