Re: Severe ASOC runtime bug
Re: Severe ASOC runtime bug
On 21 Jan 2011, at 15:43, Dave wrote:
>
> On Jan 21, 2011, at 4:02 AM, email@hidden wrote:
>
>> I don't know that you can assume that memory will not become exhausted in your loop.
>
> I'm not assuming it, I've proved it by investigating how much memory each instance takes. For 5,000 items the real memory use for that test application is 18MB. Obviously, 10,000 items should take no more than 36 MB, not 1.1GB plus.
>
Sorry. What I meant to convey was that loops that relentlessly allocate objects without being aware of how those objects will be disposed of can exhaust all available memory.
>
>> To investigate the problem I would:
>>
>> 1. try running the allocation loop in another method to applicationDidFinishLaunching_ : use a delayed selector.
>> 2. what occurs if setString_ becomes setInt_ and the integer is saved rather than the coerced string
>> 3. define a NSMutableDictionary property and use a timer to allocate the AsObjC objects incrementally (say 1000 at a time).
>> 4. try running the collector manually - see NSGarbageCollector
>> 5. use Shark and Instruments
>
> I've already done several of these good suggestions. I've spent many hours testing and creating simple test cases that cause the run-time errors plaguing my application. In my opinion, I've seen this problem enough times that I think it will always occur once you allocate enough script instance, so trying to bypass it is a waste of time.
>
My sympathies.
It is probably bug filing time, unless someone on the inside is listening and cares to chip in...
Regards
Jonathan Mitchell
Developer
Mugginsoft LLP
http://www.mugginsoft.com _______________________________________________
Do not post admin requests to the list. They will be ignored.
applescriptobjc-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden