• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cleaning up after a script
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cleaning up after a script


  • Subject: Re: Cleaning up after a script
  • From: Philip Aker <email@hidden>
  • Date: Tue, 17 Feb 2009 12:10:23 -0800

On 2009-02-17, at 09:27:01, Jay Louvion wrote:

> I am indeed receiving an error –2707 from the rear–end of a script
> saved as an application and launched from the script menu in Leopard
> 10.5.6. I know it means “Internal table overflow” but have no idea
> how to deal with that and precisely what it means.



I think some more detail would be needed before anyone could hazard a
reasonable guess. If you're trying to read a 5 Gig file, all bets are
off!

Obviously :D – No, the most CPU and memory consuming operations seems to be filing through alias lists of about 1000 odd jpeg files, splitting them into two lists (good and bad) and keeping track of the physical sizes of these two lists.

The thing is I believe that there is no error if the script is not an application. And I really would like to have it as an application, so I can activate it and force-quit it if it hangs...

I think you could first of all check about Yvan's suggestion for properties left stuffed.
For instance use a 'quit' handler to empty any properties that are lists or make sure that when you're finished processing a list, set it to {}.


Emmanuel remarked about AppleScript default memory allocation. That could have some bearing as well because you say it runs in Script Editor -- which may have a different runtime than applets. This default memory allocation can be regulated with a resource setting but in my experience, the defaults are usually good enough. Maybe the easiest way to determine if the applet's at fault is to reformat the script into an AppleScript Studio Droplet and see if that solves the problem. If you haven't dealt with AppleScript Studio apps before, don't worry, the droplet format is such that you can probably just copy and paste most of your script.


The full error runs as such: “Could not save to this script because of a system (OSA) error. -2707”



Philip Aker echo email@hidden@nl | tr a-z@. p-za-o.@

Democracy: Two wolves and a sheep voting on lunch.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users

This email sent to email@hidden
References: 
 >Re: Cleaning up after a script (From: Jay Louvion <email@hidden>)

  • Prev by Date: Weird iTunes Problem
  • Next by Date: Re: Mail windows
  • Previous by thread: Re: Cleaning up after a script
  • Next by thread: Re: Cleaning up after a script
  • Index(es):
    • Date
    • Thread