search

flatironinstitute / mountainsort

Spike sorting software
48 stars 16 forks source link

std::bad_alloc #36

Closed chengtang827 closed 6 years ago

chengtang827 commented 6 years ago

I have data from one channel, around 1 GB size. When I ran it in a 4 GB RAM Virtual Box, I got the std::bad_alloc error, so I segmented the whole data into four equal chunks with 1/4 GB each and sorted them one by one.

But when I shift to a Linux machine with 16 GB RAM, I still get the std::bad_alloc error when running the 1 GB data, and I still have to break them into 1/4 GB segments. So is this the issue of memory size? Why isn't the problem alleviated when I use larger memory?

magland commented 6 years ago

Could you please track the memory usage using a tool like top to determine whether it is running out of RAM. (I do admit that 1GB size is very small -- i don't expect it to run out of memory). Could you upload the dataset to our mlstudy web system? We can then test it there. Contact me by email for instructions on that.

magland commented 6 years ago

Closing, because this has been resolved. There was a bug that we fixed.