dirkdebruin

Max 8.2 beta crashes when using one of my latest projects that works fine on 8.1.11

I have trimmed down the patch to find the source and I think it is related to nearestpix in jit.gen. It only crashes when using a matrix with 5 or more dimensions. Sometimes it crashes right away when changing to 5 or more dimensions, and sometimes it crashes when closing the patcher.

I'm on an M1 mac mini, which overall shows some significant performance improvement with 8.2 compared to 8.1.11 so far. 

8.2 crash test.maxpat

I'm on an M1 mac mini, which overall shows some significant performance improvement with 8.2 compared to 8.1.11 so far. 


Max 8.2 beta crashes when using one of my latest projects that works fine on 8.1.11
I have trimmed down the patch to find the source and I t

crash-report-1

Okay. AFAICT, the code for converting smaller vectors to larger vectors in jit.gen, are not zero padding the arrays that the smaller vectors are copied into if those larger vectors are of size greater than 4. Examining the code, this doesn't look particularly new. However, it could be that under previous versions, the memory allocation conditions were zeroing memory themselves and wouldn't have required any logic to do so or things were just very lucky. I have some more experimentation to do here.

In the meantime, if you want a patch that works, you may zero pad your smaller vectors to whatever the larger vector you will be converting them to. In this case the [- 1 0] can be replaced with [- 1 0 0 0 0 0 0 0] or however many zeros you need to match the dim count.

Thanks! That seems to fix the problem and is probably good practice to be doing anyway. 

I'm probably not going to change the dim count dynamically so it is not going to be a problem for me anymore but it might be good to give the object a default behaviour for these situations anyway.

Thanks! That seems to fix the problem and is probably good practice to be doing anyway. 
I'm probably not going to change the dim count dynamically so it is not going to be a problem for me anymore but it might be good to give the object a default behaviour for these situations anyway. 

crash report