7391

It can be a coincidence but a patch of mine is playing 3 or 4 times a week on show for two month and it crashes on march the 4 and the 24 at 22:37:52 and 22:38:36. Aparently all the automatic tasks are disabled but perhaps do I forget something.

A strange thing about these crashes : the screen was black - no message, no finder… but the computer was still on.

The only other thing I can think about : that's a moment in the show where light people and sound people interract together on the patch. Light configures omx via Art-net (DMX via ethernet)and sound loads some buffers. Can I have a problem of priority or something ?

PS_I join one of the crash report. Both are exactly the same.

Hi
It can be a coincidence but a patch of mine is playing 3 or 4 times a week on show for two month and it crashes on march the 4 and the 24 at 22:37:52 and 22:38:36. Aparently all the automatic tasks are disabled but perhaps do I forget something.

PS_I join one of the crash report. Both are exactly the same.


midnight-hour-of-the-crash

The crash seems to be related to udpreceive.


Can I ask you why you think the udpreceive is the problem ?

The Mac pro I use for this patch was set up in 10.6 but I needed udp and it didn't work. I installed a clone copy of a 10.5.8 system and everything was ok… except these crash

Thanks A LOT Patrick
Can I ask you why you think the udpreceive is the problem ?
The Mac pro I use for this patch was set up in 10.6 but I needed udp and it didn't work. I installed a clone copy of a 10.5.8 system and everything was ok… except these crash


it will ound silly but i want to say it :

isn't your "crash" related to you having programmed your computer to shut down or sleep mode on 22:38 ? :)

it will ound silly but i want to say it :
isn't your "crash" related to you having programmed your computer to shut down or sleep mode on 22:38 ? :)


maybe you leant those kind of things by "disabled automatic tasks". so it's even sillier. never mind.

0 libSystem.B.dylib     0xffff061a __bzero + 26 (cpu_capabilities.h:244)

1 libSystem.B.dylib     0x965743c8 strncpy + 216

2 com.cycling74.MaxMSPRuntime     0x0001c3d7 typedmess_fun + 1283

3 com.cycling74.MaxMSPRuntime     0x0005ee1b outlet_anything + 727

4 com.cycling74.MaxAPI     0x0962e9b1 outlet_anything + 60

5 com.cycling74.udpreceive     0x30284571 udprecv_callback + 85

6 com.cycling74.udpreceive     0x30283b30 udpreceiver_clock_tick + 58

7 com.cycling74.MaxMSPRuntime     0x00029a5f sched_takepoll + 483

8 com.cycling74.MaxMSPRuntime     0x00029b14 sched_poll + 50

9 com.cycling74.MaxMSPRuntime     0x00061f0a systimer_pollaction + 50

10 com.cycling74.MaxMSPRuntime     0x00062344 mactimer_isr() + 100

11 ...ple.CoreServices.CarbonCore    0x96186a4b TimerThread + 237

12 libSystem.B.dylib     0x9657d155 _pthread_start + 321

13 libSystem.B.dylib     0x9657d012 thread_start + 34

Can I ask you why you think the udpreceive is the problem ?
 

Thread 5 Crashed:
0   libSystem.B.dylib             	0xffff061a __bzero + 26 (cpu_capabilities.h:244)
1   libSystem.B.dylib             	0x965743c8 strncpy + 216
2   com.cycling74.MaxMSPRuntime   	0x0001c3d7 typedmess_fun + 1283
3   com.cycling74.MaxMSPRuntime   	0x0005ee1b outlet_anything + 727
4   com.cycling74.MaxAPI          	0x0962e9b1 outlet_anything + 60
5   com.cycling74.udpreceive      	0x30284571 udprecv_callback + 85
6   com.cycling74.udpreceive      	0x30283b30 udpreceiver_clock_tick + 58
7   com.cycling74.MaxMSPRuntime   	0x00029a5f sched_takepoll + 483
8   com.cycling74.MaxMSPRuntime   	0x00029b14 sched_poll + 50
9   com.cycling74.MaxMSPRuntime   	0x00061f0a systimer_pollaction + 50
10  com.cycling74.MaxMSPRuntime   	0x00062344 mactimer_isr() + 100
11  ...ple.CoreServices.CarbonCore	0x96186a4b TimerThread + 237
12  libSystem.B.dylib             	0x9657d155 _pthread_start + 321
13  libSystem.B.dylib             	0x9657d012 thread_start + 34

Midnight, hour of the crash