Hi Mark and thx for the reply,
I don’t think so. I put all the error message :
Estimated memory for full processing: 9806.98MB (avail.: 256 MB), optimal image partitioning: 39 blocks
2020-10-07 17:55:24 (INFO): Estimation will be performed in 40 blocks of 15360x322 pixels
Computing stats on input image …: 100% [**************************************************] (19s)
2020-10-07 18:09:56 (FATAL) LargeScaleMeanShift: Caught std::exception during application execution: bad allocation
Dear @kadirim,
Your issue looks very similar to what @wkcmark describes here. I will try to reproduce your bug, to understand what happens.
Best regards.
Julien.
Does the procedure work with a subset of the image? You could it to crop a much smaller portion and check if it runs then. If not then there is a deeper problem, if it runs through then it might be “simply” a memory problem