Author here. Sorry that it's giving you a hard time. Can you say what OS X version you're running or provide any other details so I can try and reproduce/fix?
(You can email me privately at finda@keminglabs.com)
I tested with a dozen folks before releasing and this issue never came up.
Haven't heard from OP, but another person emailed me and the issue is likely because Finda relies on AVX2 CPU instructions for fast search. These instructions were introduced in 2012, so it's likely the OP was running on older hardware.
I'll add CPU detection to a future version of Finda so that it can fallback to slower, non-vectorized instructions.
I tested with a dozen folks before releasing and this issue never came up.