Re: AppleScript crashes constantly
Re: AppleScript crashes constantly
- Subject: Re: AppleScript crashes constantly
- From: Emmanuel <email@hidden>
- Date: Tue, 13 Feb 2001 13:46:48 +0100
At 13:35 +0100 13/02/01, Wim Melis wrote:
>
>
But even if I compile and run a simple handler like:
>
>
on test(a)
>
set b to a
>
return b
>
end
>
>
The results aren't consistent, after multiple runs sometimes it'll give
>
the same 'cumulated diff', and sometimes it'll hop a few bytes up or down
>
and stay there for a few iterations, etc.
In order to achieve perfect reproducibility, you need not change anything
to the state of the computer.
For instance, if you swap front / background two (irrelevant) windows, you
might make visible a control (a button, say) which was not before. This
will imply allocating a quickdraw region to get updated, thus burning RAM.
>
So, am I using it correctly? Is there a faster way that doen't involve
>
those excursions to the output window?
I am not sure why you are using an output window.
I recall that if you append the colon ":" after a given script, and you run
it, it remains silent (no output wherever).
>
And what is 'current free' exactly? Is it some chunk of reserved memory
>
in the OS?
I suppose it is the size of the largest block. In Smile, whose memory
management is rather optimal, the largest block size should be very close
to the total available memory.
Best regards,
Emmanuel