Alex

Upd: I think first version (with operator = ) works on small datasets yet, however fails on big which are close to use swap.

I have 3 copy-pastes similar. 2 of them did crash periodically. 3rd - never. Also when I said "small data" that was hand-crafted while real data are from web some....

More info:  Used function: ``` //this is work around of opeartor = used before, as it was crashing with SIMD template void move_to_row(tensors::result_t& res, const size_t row, ViewClass&& src)...

If I do this: `auto&& e = xt::eval(src); that fails here, which is original current / another - 1.

One more try to split it 

Maybe wrong pointer? Not sure ... 

More to go, fails: ``` using tensor_vector_t = xt::xtensor; const tensor_vector_t another = xt::eval(xt::view(src, i + rows, xt::all())); ``` Where src is slice of cube on constant field: `return xt::view(tensor,...

Interesting, this removes error, when I do eval slice: `const auto src = xt::eval(parsed.viewByField(1));` which evals `return xt::view(tensor, field, xt::all(), xt::all());` That has sence, in crafted tests not all fields...

Fails here:Mailbox::executeQPU on sending ioctl, everything hangs as > [VC4CL] Running work-group 0, 0, 0 > [VC4CL] Mailbox buffer before: > [VC4CL] 0000: 0x00000028 > [VC4CL] 0004: 0x00000000 > [VC4CL]...