please help, what are these crashes

getting these constantly, any ideas what the root of this is? Thread 8 Crashed: 0 com.cockos.reaper 0x0056285f __intel_new_memcpy + 2271 1 com.cockos.reaper 0x000a4697 MediaTrack::RenderSamples(double, long long, int, Track_RS_Output*, int, double, MediaTrack**, int, midi_List*, int, int, int, int, int, MediaTrack::Track_SendRec*) + 3287 2 com.cockos.reaper 0x0009f2ca MediaTrack::RenderSamples_nocache(double, long long, double*, int, int, double, MediaTrack**, int, int*, bool, int, int) + 19546 3 com.cockos.reaper 0x000a4697 MediaTrack::RenderSamples(double, long long, int, Track_RS_Output*, int, double, MediaTrack**, int, midi_List*, int, int, int, int, int, MediaTrack::Track_SendRec*) + 3287 4 com.cockos.reaper 0x0009f2ca MediaTrack::RenderSamples_nocache(double, long long, double*, int, int, double, MediaTrack**, int, int*, bool, int, int) + 19546 5 com.cockos.reaper 0x000a4697 MediaTrack::RenderSamples(double, long long, int, Track_RS_Output*, int, double, MediaTrack**, int, midi_List*, int, int, int, int, int, MediaTrack::Track_SendRec*) + 3287 6 com.cockos.reaper 0x00095ccb MediaTrack::RunWorkThread(int, double, MediaTrack**, int) + 1707 7 com.cockos.reaper 0x000d6f76 WorkerThreadInst::threadProc(void*) + 1318 8 com.cockos.reaper 0x0035095f __threadproc(void*) + 31 9 libSystem.B.dylib 0x9063d259 _pthread_start + 345 10 libSystem.B.dylib 0x9063d0de thread_start + 34 more crash logs -

In what context are these crashes? (When you do XZ or open Z under a full moon etc.)

crash happens within about 30 seconds after opening a specific project. No other criteria necessary :)

still getting these constantly as projects grow - someone must be able to disern what some of this means Thread 107 Crashed: 0 com.cockos.reaper 0x005690bf __intel_new_memcpy + 2271 1 com.cockos.reaper 0x000a5037 MediaTrack::RenderSamples(double, long long, int, Track_RS_Output*, int, double, MediaTrack**, int, midi_List*, int, int, int, int, int, MediaTrack::Track_SendRec*) + 3287 2 com.cockos.reaper 0x000a0392 MediaTrack::RenderSamples_nocache(double, long long, double*, int, int, double, MediaTrack**, int, int*, bool, int, int) + 19666 3 com.cockos.reaper 0x000a5037 MediaTrack::RenderSamples(double, long long, int, Track_RS_Output*, int, double, MediaTrack**, int, midi_List*, int, int, int, int, int, MediaTrack::Track_SendRec*) + 3287 4 com.cockos.reaper 0x000a0392 MediaTrack::RenderSamples_nocache(double, long long, double*, int, int, double, MediaTrack**, int, int*, bool, int, int) + 19666 5 com.cockos.reaper 0x000a5037 MediaTrack::RenderSamples(double, long long, int, Track_RS_Output*, int, double, MediaTrack**, int, midi_List*, int, int, int, int, int, MediaTrack::Track_SendRec*) + 3287 6 com.cockos.reaper 0x0009600b MediaTrack::RunWorkThread(int, double, MediaTrack**, int) + 1707 7 com.cockos.reaper 0x000d7926 WorkerThreadInst::threadProc(void*) + 1318 8 com.cockos.reaper 0x00355c8f __threadproc(void*) + 31 9 libSystem.B.dylib 0x9063d259 _pthread_start + 345 10 libSystem.B.dylib 0x9063d0de thread_start + 34

From the crash log I infer this is on a Mac OS? If so please follow and try to give more information. Specifically what MacOS version and how and when does the bug manifest. The crash report itself means the program crashes in the function __intel_new_memcpy and this function was called by the function call sequence listed below in the crash report. EDIT: Though this report alone won't help the developers fix the problem, because this call sequence is most likely what is expected regular behavior and the only deviation from regular behavior is the crash at the end. So what is needed to help the developers fix the problem is the WHEN and HOW this problem occurs so they can comprehend what is going on. Hence you should find a way, e.g. small project to reproduce the problem or even simply remembering exactly what you did right prior to the crash can help a lot.

I ran into this same type of behaviour as the above crash on another project recently. I went through extensive troubleshooting with no success. Eventually I found that running the same project in 64bit was absolutly rock solid. I sent a detailed report to support over 10 days ago, and am still waiting for a response.

Your right. It's knocking my confidence with cockos as I've had about 5 crashes today alone!!

gwok, we have your emails, thank you for sending them. We fell a bit behind over the holidays, but we'll get on this now.

Can you check the RAM use of REAPER before these crashes? This sounds like you are running out of address space (you may wish to try using REAPER64, or using bridging on some of the more RAM-intensive plug-ins).

Thanks Schwa but I think what I and the others were worried about is that we haven't changed any Plug ins or installed anything new and with 32bit I could load a heap of stuff and Reaper never flinched, which it's famous for! Since 4.14 it seems a little flaky now doing the same stuff which is a little worryinp