please describe ASExecuteEvent, UASLookupIDForScript

hey y’all

i have an app that parses tons of data and does magic tricks

it runs great with smaller amounts of data

but when it runs for several minutes with tons of data it crashes like this :

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000002

VM Regions Near 0x2:

__TEXT 0000000106710000-0000000106711000 [ 4K] r-x/rwx SM=COW

Application Specific Information:
Performing @selector(ButtonClickRun:) from sender NSButton 0x60000015c1a0

Thread 0 Crashed:: Dispatch queue:
0 UASLookupIDForScript(TUASScript const*) + 51
1 UASRemoteSend(unsigned char, unsigned char, unsigned char, unsigned char, unsigned char, unsigned char*) + 163
2 UASActor_Send(unsigned char, unsigned char, unsigned char) + 396
3 UASValue_Send(unsigned char, unsigned char, TUASClassIndex, unsigned char) + 329
4 UASExecute1() + 321
5 ASExecuteEvent(AEDesc const*, unsigned int, int, unsigned int*) + 625
6 AppleScriptComponent + 845
7 OSAExecuteEvent + 70
8 +[BAObjectProto invokeScriptHandler:forObject:inComponentInstance:args:error:] + 222
9 -[BAObjectProto invokeScriptHandler:args:error:] + 114
10 -[BAObjectProto forwardInvocation:] + 383
11 forwarding + 452
12 _CF_forwarding_prep_0 + 120

i can’t find any documentation on UASLookupIDForScript

i’m trying to figure out what it’s doing at the time of the crash

the line that says : ASExecuteEvent(AEDesc const*, unsigned int, int, unsigned int*)

does it mean that one of my handlers was just called with four parameters ?

or is my problem unrelated to what was going on and more related to memory deallocation

i’ve had this crash with xcode 4 running on lion with and without garbage collection

now on xcode 5 and 10.9 with and without arc i’m having the same crashes

any info or pointers to documentation would be much appreciated




See my reply to the same message you posted on the ASObjC mailing list.

thanks for the reply shane

if i resolve this conclusively, i’ll post back to both forums

happy trails

In the meantime, if you can build a relatively simple project that reproduces the problem, please do log a bug report.