instacrash with fluid.datasetquery~

[rconstanzo]

Having a hard time reproducing it, but I do have a crash report. Basically I was building up a query for fluid.datasetquery~ and got an instacrash when sending this message:
clear, filter 44 > 2000., addrange 0 44, transform coll dump

I can supply the dataset/patch if desired, but as mentioned I'm having a hard time reproducing it.

Pretty sure I'm on the latest/release (version 1.0.0+sha.d0e42a3.core.sha.f86443a).

Crash report attached but crashed thread starts with:

Thread 0 Crashed:: CrBrowserMain  Dispatch queue: com.apple.main-thread
0   org.flucoma.fluid.libmanipulation	0x0000000128182615 fluid::algorithm::DataSetQuery::process(fluid::FluidDataSet<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, double, 1l> const&, fluid::FluidDataSet<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, double, 1l>&, fluid::FluidDataSet<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, double, 1l>&) + 677

crash.zip

[weefuzzy]

Yeah, if you can send sample data, that would be good. Nothing much else to go on otherwise.

[rconstanzo]

I don't know what exact data I was using when I got this crash, but these are the types of data that it would have been.

Archive.zip

(at the time I don't know if I was using transformjoin yet to use one dataset to query another, but in any case, the data dataset.json is identical in structure to what I would have used when I got this crash.