Oops, Michael is right, I mistyped it. Sorry about that.
> Hi Curtis, Christophe,
>
> I think it should be the Library/Logs/CrashReporter (probably the user
> library, not the system-wide one) - at least in OS X 10.4
> It will be named something like JavaApplicationStub.crash.log
>
> Michael
> ________________________________________________________________
>
>
> On 17 Dec 2009, at 18:38, Curtis Rueden wrote:
>
> Hi Christophe,
>>
>> The ImageJ progress bar freezes, I get the rainbow spinning beachball for
>> a
>>
>>> few
>>> seconds and then ImageJ quits. Next time I get that, can you tell me
>>> where
>>> I
>>> can find a log that could be useful to determine the exact problem such
>>> as
>>> the one at the start of this discussion ?
>>>
>>>
>> Since it is a native stack trace, I am guessing that Gaurav got it from
>> the
>> Crash Reporter, which should pop up automatically when the application
>> crashes. According to Apple, crash logs are typically placed in
>> ~/Applications/Logs/CrashReporter, or sometimes in
>> /Applications/Logs/CrashReporter.
>>
>> -Curtis
>>
>> On Thu, Dec 17, 2009 at 3:28 AM, Christophe Leterrier <
>>
[hidden email]> wrote:
>>
>> Hi Curtis,
>>>
>>> It is difficult to say because it does not seem to be a deterministic
>>> crash.
>>> It happens usually when I'm working on merging stacks of images (around
>>> 30
>>> to 100 512x512 images, four 16-bits and one RGB stacks at once for RGB
>>> merge). I have the impression that the crash always occur either when
>>> importing or exporting one of those stacks from/to an image sequence. The
>>> ImageJ progress bar freezes, I get the rainbow spinning beachball for a
>>> few
>>> seconds and then ImageJ quits. Next time I get that, can you tell me
>>> where
>>> I
>>> can find a log that could be useful to determine the exact problem such
>>> as
>>> the one at the start of this discussion ?
>>>
>>> Thanks
>>>
>>> Christophe
>>>
>>>