Georg Hajdu

I have regular crashes with Jitter. They occur after a certain amount 

of time, even with no user interaction, i.e. leaving the computer 

Path: /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP

Codes: KERN_INVALID_ADDRESS (0x0001) at 0xffe5e5ee

0 com.apple.QuickTime     0x942fc150 callBackTask_priv + 190

1 com.apple.QuickTime     0x943426e1 TaskMovie_priv + 1286

2 com.apple.QuickTime     0x9440c5c9 frequentlyTaskMovies + 

3 com.apple.HIToolbox     0x92e12c41 TimerVector + 31

4 com.apple.CoreFoundation     0x9082b822 CFRunLoopRunSpecific + 

5 com.apple.CoreFoundation     0x9082ab0e CFRunLoopRunInMode + 61

6 com.apple.HIToolbox     0x92ddabef 

7 com.apple.HIToolbox     0x92dda2fd ReceiveNextEventCommon 

8 com.apple.HIToolbox     0x92e22c8f _AcquireNextEvent + 58

9 com.apple.HIToolbox     0x92e22ad0 

10 com.cycling74.MaxMSP46     0x000268de app_run + 52 (main.c: 

11 com.cycling74.MaxMSP46     0x00026b88 main + 680 (main.c:415)

12 com.cycling74.MaxMSP46     0x00001da2 _start + 216

13 com.cycling74.MaxMSP46     0x00001cc9 start + 41

I have regular crashes with Jitter. They occur after a certain amount  
of time, even with no user interaction, i.e. leaving the computer  
unattended.

Date/Time:      2007-02-26 17:05:02.165 +0100
OS Version:     10.4.8 (Build 8N1037)
Report Version: 4

Command: MaxMSP
Path:    /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP
Parent:  WindowServer [63]

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0xffe5e5ee

Thread 0 Crashed:
0   com.apple.QuickTime            	0x942fc150 callBackTask_priv + 190
1   com.apple.QuickTime            	0x943426e1 TaskMovie_priv + 1286
2   com.apple.QuickTime            	0x9440c5c9 frequentlyTaskMovies +  
143
3   com.apple.HIToolbox            	0x92e12c41 TimerVector + 31
4   com.apple.CoreFoundation       	0x9082b822 CFRunLoopRunSpecific +  
3341
5   com.apple.CoreFoundation       	0x9082ab0e CFRunLoopRunInMode + 61
6   com.apple.HIToolbox            	0x92ddabef  
RunCurrentEventLoopInMode + 285
7   com.apple.HIToolbox            	0x92dda2fd ReceiveNextEventCommon  
+ 385
8   com.apple.HIToolbox            	0x92e22c8f _AcquireNextEvent + 58
9   com.apple.HIToolbox            	0x92e22ad0  
RunApplicationEventLoop + 150
10  com.cycling74.MaxMSP46         	0x000268de app_run + 52 (main.c: 
1458)
11  com.cycling74.MaxMSP46         	0x00026b88 main + 680 (main.c:415)
12  com.cycling74.MaxMSP46         	0x00001da2 _start + 216
13  com.cycling74.MaxMSP46         	0x00001cc9 start + 41


intermittent-crashes-with-jitter

Weird, this is the same crash reported by Scott Fitzgerald the other 

day. It's a crash in an automatic QuickTime task, apparently 

involving a callback. Whether it's our callback or not, is hard to 

say. Are you doing anything with looppoints in your patch?

Am 26.02.2007 um 18:07 schrieb Georg Hajdu:

> I have regular crashes with Jitter. They occur after a certain 

> amount of time, even with no user interaction, i.e. leaving the 

> Date/Time: 2007-02-26 17:05:02.165 +0100

> Path: /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP

> Codes: KERN_INVALID_ADDRESS (0x0001) at 0xffe5e5ee

> 0 com.apple.QuickTime     0x942fc150 callBackTask_priv + 190

> 1 com.apple.QuickTime     0x943426e1 TaskMovie_priv + 1286

> 2 com.apple.QuickTime     0x9440c5c9 frequentlyTaskMovies 

> 3 com.apple.HIToolbox     0x92e12c41 TimerVector + 31

> 4 com.apple.CoreFoundation     0x9082b822 CFRunLoopRunSpecific 

> 5 com.apple.CoreFoundation     0x9082ab0e CFRunLoopRunInMode + 61

> 6 com.apple.HIToolbox     0x92ddabef 

> 7 com.apple.HIToolbox     0x92dda2fd 

> 8 com.apple.HIToolbox     0x92e22c8f _AcquireNextEvent + 58

> 9 com.apple.HIToolbox     0x92e22ad0 

> 10 com.cycling74.MaxMSP46     0x000268de app_run + 52 (main.c: 

> 11 com.cycling74.MaxMSP46     0x00026b88 main + 680 (main.c:415)

> 12 com.cycling74.MaxMSP46     0x00001da2 _start + 216

> 13 com.cycling74.MaxMSP46     0x00001cc9 start + 41

Weird, this is the same crash reported by Scott Fitzgerald the other  
day. It's a crash in an automatic QuickTime task, apparently  
involving a callback. Whether it's our callback or not, is hard to  
say. Are you doing anything with looppoints in your patch?

> I have regular crashes with Jitter. They occur after a certain  
> amount of time, even with no user interaction, i.e. leaving the  
> computer unattended.
>
> See crash report.
>
> Georg
>
> Date/Time:      2007-02-26 17:05:02.165 +0100
> OS Version:     10.4.8 (Build 8N1037)
> Report Version: 4
>
> Command: MaxMSP
> Path:    /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP
> Parent:  WindowServer [63]
>
> Version: ??? (4.6.3)
>
> PID:    2882
> Thread: 0
>
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_INVALID_ADDRESS (0x0001) at 0xffe5e5ee
>
> Thread 0 Crashed:
> 0   com.apple.QuickTime            	0x942fc150 callBackTask_priv + 190
> 1   com.apple.QuickTime            	0x943426e1 TaskMovie_priv + 1286
> 2   com.apple.QuickTime            	0x9440c5c9 frequentlyTaskMovies  
> + 143
> 3   com.apple.HIToolbox            	0x92e12c41 TimerVector + 31
> 4   com.apple.CoreFoundation       	0x9082b822 CFRunLoopRunSpecific  
> + 3341
> 5   com.apple.CoreFoundation       	0x9082ab0e CFRunLoopRunInMode + 61
> 6   com.apple.HIToolbox            	0x92ddabef  
> RunCurrentEventLoopInMode + 285
> 7   com.apple.HIToolbox            	0x92dda2fd  
> ReceiveNextEventCommon + 385
> 8   com.apple.HIToolbox            	0x92e22c8f _AcquireNextEvent + 58
> 9   com.apple.HIToolbox            	0x92e22ad0  
> RunApplicationEventLoop + 150
> 10  com.cycling74.MaxMSP46         	0x000268de app_run + 52 (main.c: 
> 1458)
> 11  com.cycling74.MaxMSP46         	0x00026b88 main + 680 (main.c:415)
> 12  com.cycling74.MaxMSP46         	0x00001da2 _start + 216
> 13  com.cycling74.MaxMSP46         	0x00001cc9 start + 41
>


On Feb 26, 2007, at 6:24 PM, Jeremy Bernstein wrote:

> Are you doing anything with looppoints in your patch?

anton and i also see this crash, with loopreport 1. it is 

intermittent, untraceable and incredibly frustrating.

On Feb 26, 2007, at 12:24 PM, Jeremy Bernstein wrote:

> Weird, this is the same crash reported by Scott Fitzgerald the 

> other day. It's a crash in an automatic QuickTime task, apparently 

> involving a callback. Whether it's our callback or not, is hard to 

> say. Are you doing anything with looppoints in your patch?

> Am 26.02.2007 um 18:07 schrieb Georg Hajdu:

>> I have regular crashes with Jitter. They occur after a certain 

>> amount of time, even with no user interaction, i.e. leaving the 

>> Date/Time: 2007-02-26 17:05:02.165 +0100

>> Path: /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP

>> Codes: KERN_INVALID_ADDRESS (0x0001) at 0xffe5e5ee

>> 0 com.apple.QuickTime     0x942fc150 callBackTask_priv + 

>> 1 com.apple.QuickTime     0x943426e1 TaskMovie_priv + 1286

>> 2 com.apple.QuickTime     0x9440c5c9 

>> 3 com.apple.HIToolbox     0x92e12c41 TimerVector + 31

>> 4 com.apple.CoreFoundation     0x9082b822 

>> 5 com.apple.CoreFoundation     0x9082ab0e CFRunLoopRunInMode 

>> 6 com.apple.HIToolbox     0x92ddabef 

>> 7 com.apple.HIToolbox     0x92dda2fd 

>> 8 com.apple.HIToolbox     0x92e22c8f _AcquireNextEvent + 58

>> 9 com.apple.HIToolbox     0x92e22ad0 

anton and i also see this crash, with loopreport 1.  it is  
intermittent, untraceable and incredibly frustrating.

> Weird, this is the same crash reported by Scott Fitzgerald the  
> other day. It's a crash in an automatic QuickTime task, apparently  
> involving a callback. Whether it's our callback or not, is hard to  
> say. Are you doing anything with looppoints in your patch?
>
> jb
>
> Am 26.02.2007 um 18:07 schrieb Georg Hajdu:
>
>> I have regular crashes with Jitter. They occur after a certain  
>> amount of time, even with no user interaction, i.e. leaving the  
>> computer unattended.
>>
>> See crash report.
>>
>> Georg
>>
>> Date/Time:      2007-02-26 17:05:02.165 +0100
>> OS Version:     10.4.8 (Build 8N1037)
>> Report Version: 4
>>
>> Command: MaxMSP
>> Path:    /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP
>> Parent:  WindowServer [63]
>>
>> Version: ??? (4.6.3)
>>
>> PID:    2882
>> Thread: 0
>>
>> Exception:  EXC_BAD_ACCESS (0x0001)
>> Codes:      KERN_INVALID_ADDRESS (0x0001) at 0xffe5e5ee
>>
>> Thread 0 Crashed:
>> 0   com.apple.QuickTime            	0x942fc150 callBackTask_priv +  
>> 190
>> 1   com.apple.QuickTime            	0x943426e1 TaskMovie_priv + 1286
>> 2   com.apple.QuickTime            	0x9440c5c9  
>> frequentlyTaskMovies + 143
>> 3   com.apple.HIToolbox            	0x92e12c41 TimerVector + 31
>> 4   com.apple.CoreFoundation       	0x9082b822  
>> CFRunLoopRunSpecific + 3341
>> 5   com.apple.CoreFoundation       	0x9082ab0e CFRunLoopRunInMode  
>> + 61
>> 6   com.apple.HIToolbox            	0x92ddabef  
>> RunCurrentEventLoopInMode + 285
>> 7   com.apple.HIToolbox            	0x92dda2fd  
>> ReceiveNextEventCommon + 385
>> 8   com.apple.HIToolbox            	0x92e22c8f _AcquireNextEvent + 58
>> 9   com.apple.HIToolbox            	0x92e22ad0  
>> RunApplicationEventLoop + 150
>> 10  com.cycling74.MaxMSP46         	0x000268de app_run + 52  
>> (main.c:1458)
>> 11  com.cycling74.MaxMSP46         	0x00026b88 main + 680 (main.c: 
>> 415)
>> 12  com.cycling74.MaxMSP46         	0x00001da2 _start + 216
>> 13  com.cycling74.MaxMSP46         	0x00001cc9 start + 41
>>
>
>


Ive also had these crashes on my own performance patch with similar 

looking crash logs, if its worth mentioning.

On Feb 26, 2007, at 6:35 PM, Georg Hajdu wrote:

> On Feb 26, 2007, at 6:24 PM, Jeremy Bernstein wrote:

>> Are you doing anything with looppoints in your patch?

Ive also had these crashes on my own performance patch with similar  
looking crash logs, if its worth mentioning.

> Hi Jeremy,
>
> Yes, I am.
>
> Georg
>
> On Feb 26, 2007, at 6:24 PM, Jeremy Bernstein wrote:
>
>> Are you doing anything with looppoints in your patch?
>

Your use of looppoints would be more worth mentioning - aye or nay?

> Ive also had these crashes on my own performance patch with similar 

> looking crash logs, if its worth mentioning.

> Ive also had these crashes on my own performance patch with similar  
> looking crash logs, if its worth mentioning.


yup! I do indeed loop it up! Sorry I thought that was implied :) Ill 

have a few movies going, like 3 playback with different looppoints 

etc. I do not use loop report however, and I usually just use 

On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:

> Your use of looppoints would be more worth mentioning - aye or nay?

>> Ive also had these crashes on my own performance patch with 

>> similar looking crash logs, if its worth mentioning.

yup! I do indeed loop it up! Sorry I thought that was implied :) Ill  
have a few movies going, like 3 playback with different looppoints  
etc. I do not use loop report however, and I usually just use  
straight looping, no palindrome, etc.

> Your use of looppoints would be more worth mentioning - aye or nay?
>
> jb
>
> Am 27.02.2007 um 07:19 schrieb vade:
>
>> Ive also had these crashes on my own performance patch with  
>> similar looking crash logs, if its worth mentioning.

maybe a bit more worth mentioning, i never saw that patch crash in

but in 4.6, jit 1.6 it started showing up

i limited the number of getframe requests and it seems to have solved

the problem (at least, I haven't gotten any calls about it since i

> On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:

maybe a bit more worth mentioning, i never saw that patch crash in
4.5.x, jitter 1.5.x

i limited the number of getframe requests and it seems to have solved
the problem (at least, I haven't gotten any calls about it since i
made the change)

> On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:
>
> Your use of looppoints would be more worth mentioning - aye or nay?


I've seen this too, I was trying to pin it down. I thought it had 

something to do with asyncread - or am I just imagining that? It 

seems to especially affect patches with 3 movies or more, but the 

other day I was doing nothing special but playing a single movie and 

In fact, I wrote a patch that used the "time X" message to play 

movies with the time messages generated according to an audio signal, 

for really tightly synchronized playback, and it crashes like 

As an aside, in my experience, quicktime on it's own does crash on 

playback - a lot. On all machines, and not doing anything special.

> yup! I do indeed loop it up! Sorry I thought that was implied :) 

> Ill have a few movies going, like 3 playback with different 

> looppoints etc. I do not use loop report however, and I usually 

> just use straight looping, no palindrome, etc.

>> Your use of looppoints would be more worth mentioning - aye or nay?

>>> Ive also had these crashes on my own performance patch with 

>>> similar looking crash logs, if its worth mentioning.

I've seen this too, I was trying to pin it down.  I thought it had  
something to do with asyncread - or am I just imagining that?  It  
seems to especially affect patches with 3 movies or more, but the  
other day I was doing nothing special but playing a single movie and  
it crashed.

In fact, I wrote a patch that used the "time X" message to play  
movies with the time messages generated according to an audio signal,  
for really tightly synchronized playback, and it crashes like  
nobody's business, so I gave it up.

As an aside, in my experience, quicktime on it's own does crash on  
playback - a lot.  On all machines, and not doing anything special.

> yup! I do indeed loop it up! Sorry I thought that was implied :)  
> Ill have a few movies going, like 3 playback with different  
> looppoints etc. I do not use loop report however, and I usually  
> just use straight looping, no palindrome, etc.
>
> On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:
>
>> Your use of looppoints would be more worth mentioning - aye or nay?
>>
>> jb
>>
>> Am 27.02.2007 um 07:19 schrieb vade:
>>
>>> Ive also had these crashes on my own performance patch with  
>>> similar looking crash logs, if its worth mentioning.
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>


That is a very interesting tidbit. I am using getime myself to update 

a scrub-able UI for the playhead. I wonder if that has anything to do 

with it. I ping it fairly regularly to get smooth motion. Ill see if 

> "As an aside, in my experience, quicktime on it's own does crash on 

> playback - a lot. On all machines, and not doing anything special."

On Feb 27, 2007, at 12:25 PM, Scott Fitzgerald wrote:

> maybe a bit more worth mentioning, i never saw that patch crash in

> but in 4.6, jit 1.6 it started showing up

> i limited the number of getframe requests and it seems to have solved

> the problem (at least, I haven't gotten any calls about it since i

>> On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:

That is a very interesting tidbit. I am using getime myself to update  
a scrub-able UI for the playhead. I wonder if that has anything to do  
with it. I ping it fairly regularly to get smooth motion. Ill see if  
that is helps at all.

> "As an aside, in my experience, quicktime on it's own does crash on  
> playback - a lot.  On all machines, and not doing anything special."

> maybe a bit more worth mentioning, i never saw that patch crash in
> 4.5.x, jitter 1.5.x
>
> but in 4.6, jit 1.6 it started showing up
>
> i limited the number of getframe requests and it seems to have solved
> the problem (at least, I haven't gotten any calls about it since i
> made the change)
>
>> On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:
>>
>> Your use of looppoints would be more worth mentioning - aye or nay?

> That is a very interesting tidbit. I am using getime myself to 

> update a scrub-able UI for the playhead. I wonder if that has 

> anything to do with it. I ping it fairly regularly to get smooth 

> motion. Ill see if that is helps at all.

>> "As an aside, in my experience, quicktime on it's own does crash 

>> on playback - a lot. On all machines, and not doing anything 

Yeah, QT player itself. Especially when scrubbing thru frames with 

I've also found that sending "rate XXX" messages to jit.qt.movie seem 

to crash jitter - but the disclaimer is, I haven't really set up a 

test patch so don't consider that a bug report, more intuition at 

this point. I will try to pin it down soon, I hope.

> On Feb 27, 2007, at 12:25 PM, Scott Fitzgerald wrote:

>> maybe a bit more worth mentioning, i never saw that patch crash in

>> but in 4.6, jit 1.6 it started showing up

>> i limited the number of getframe requests and it seems to have solved

>> the problem (at least, I haven't gotten any calls about it since i

>>> On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:

>>> Your use of looppoints would be more worth mentioning - aye or nay?

> That is a very interesting tidbit. I am using getime myself to  
> update a scrub-able UI for the playhead. I wonder if that has  
> anything to do with it. I ping it fairly regularly to get smooth  
> motion. Ill see if that is helps at all.
>
>
>> "As an aside, in my experience, quicktime on it's own does crash  
>> on playback - a lot.  On all machines, and not doing anything  
>> special."
>
> Evan - You mean QT player on its own?

Yeah, QT player itself.  Especially when scrubbing thru frames with  
some sort of temporal compression.
I've also found that sending "rate XXX" messages to jit.qt.movie seem  
to crash jitter - but the disclaimer is, I haven't really set up a  
test patch so don't consider that a bug report, more intuition at  
this point.  I will try to pin it down soon, I hope.

>
> On Feb 27, 2007, at 12:25 PM, Scott Fitzgerald wrote:
>
>> maybe a bit more worth mentioning, i never saw that patch crash in
>> 4.5.x, jitter 1.5.x
>>
>> but in 4.6, jit 1.6 it started showing up
>>
>> i limited the number of getframe requests and it seems to have solved
>> the problem (at least, I haven't gotten any calls about it since i
>> made the change)
>>
>>> On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:
>>>
>>> Your use of looppoints would be more worth mentioning - aye or nay?
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>


Hrm. Thats odd then. Do you have a bunch of extra codecs installed? 

My QT player hasnt quit in .. ages. Any oddities ive found with QT 

player can usually be trased back to an errant codec, like an older 

version of DIVX or any odd Avid codecs should you have editing 

On Feb 27, 2007, at 2:05 PM, evan.raskob [lists] wrote:

> On Feb 27, 2007, at 5:52 PM, vade wrote:

>> That is a very interesting tidbit. I am using getime myself to 

>> update a scrub-able UI for the playhead. I wonder if that has 

>> anything to do with it. I ping it fairly regularly to get smooth 

>> motion. Ill see if that is helps at all.

>>> "As an aside, in my experience, quicktime on it's own does crash 

>>> on playback - a lot. On all machines, and not doing anything 

> Yeah, QT player itself. Especially when scrubbing thru frames with 

> I've also found that sending "rate XXX" messages to jit.qt.movie 

> seem to crash jitter - but the disclaimer is, I haven't really set 

> up a test patch so don't consider that a bug report, more intuition 

> at this point. I will try to pin it down soon, I hope.

>> On Feb 27, 2007, at 12:25 PM, Scott Fitzgerald wrote:

>>> maybe a bit more worth mentioning, i never saw that patch crash in

>>> but in 4.6, jit 1.6 it started showing up

>>> i limited the number of getframe requests and it seems to have 

>>> the problem (at least, I haven't gotten any calls about it since i

>>>> On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:

>>>> Your use of looppoints would be more worth mentioning - aye or nay?

Hrm. Thats odd then. Do you have a bunch of extra codecs installed?  
My QT player hasnt quit in .. ages. Any oddities ive found with QT  
player can usually be trased back to an errant codec, like an older  
version of DIVX or any odd Avid codecs should you have editing  
systems installed.

> On Feb 27, 2007, at 5:52 PM, vade wrote:
>
>> That is a very interesting tidbit. I am using getime myself to  
>> update a scrub-able UI for the playhead. I wonder if that has  
>> anything to do with it. I ping it fairly regularly to get smooth  
>> motion. Ill see if that is helps at all.
>>
>>
>>> "As an aside, in my experience, quicktime on it's own does crash  
>>> on playback - a lot.  On all machines, and not doing anything  
>>> special."
>>
>> Evan - You mean QT player on its own?
>
> Yeah, QT player itself.  Especially when scrubbing thru frames with  
> some sort of temporal compression.
> I've also found that sending "rate XXX" messages to jit.qt.movie  
> seem to crash jitter - but the disclaimer is, I haven't really set  
> up a test patch so don't consider that a bug report, more intuition  
> at this point.  I will try to pin it down soon, I hope.
>
> -evan
>
>
>>
>> On Feb 27, 2007, at 12:25 PM, Scott Fitzgerald wrote:
>>
>>> maybe a bit more worth mentioning, i never saw that patch crash in
>>> 4.5.x, jitter 1.5.x
>>>
>>> but in 4.6, jit 1.6 it started showing up
>>>
>>> i limited the number of getframe requests and it seems to have  
>>> solved
>>> the problem (at least, I haven't gotten any calls about it since i
>>> made the change)
>>>
>>>> On Feb 27, 2007, at 4:07 AM, Jeremy Bernstein wrote:
>>>>
>>>> Your use of looppoints would be more worth mentioning - aye or nay?
>>
>> v a d e //
>>
>> www.vade.info
>> abstrakt.vade.info
>>
>>
>>
>

Intermittent crashes with Jitter