On Jan 1, 2004, at 10:35 AM, Chip Griffin wrote:

> OK, below is the latest crash information cut and pasted from the 
> crash reporter log. A brief description of how it crashes. I 
> double-click on the application. It's icon bounces about once. The 
> clock window appears but is blank. It sits there for about five 
> seconds but then the window disappears and the icon leaves the doc. I 
> then get the submit report dialog.

Chip,

thanks for the info.   I don't have a solution for you. Assuming you 
haven't hacked your system (and aren't using any software that dabbles 
with your system), this would appear to be an application failure. I'm 
also assuming you aren't seeing any other applications quitting like 
this.

Typically, I have traced these down using Robin Craig's ConsoleTracker 
(since to my knowledge Macsbug is not available in X----C.T. available 
on rel 7 ) but this requires source code which R.C. and Ted might be 
persuaded to part with in order to solve this. This failure can be 
caused by different coding errors but typically trying to access memory 
that you shouldn't is one I've seen the most often (as in accessing the 
9999th member of an array that has only 20 members). Sometimes, 
depending on machine configuration (how much memory and other 
items----mine has 1GB), some inadvertent accesses are seen by the 
memory manager as permissible, while others fail. The lurking problem 
that only manifests itself in specific scenarios is one of the most 
diabolical issues developers face.

Fortunately, this application is unlikely to be a pillar in your daily 
work, so as long as you can rule out a problem with your own system, 
just avoiding it should suffice.

Good luck.  Brian