• 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: Stack Overflow
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Stack Overflow


  • Subject: Re: Stack Overflow
  • From: Alex Zavatone <email@hidden>
  • Date: Tue, 02 Dec 2014 14:23:25 -0500

Change your diagnostic preferences to the extended one that displays debug information.

Then you should see the info that may help you debug this.

I think Tinkertool and Onyx will let you do that.

If this is not a crash, but an in app alert, in Objective-C, an NSAssert is probably being thrown and an NSAssertionHandler is probably trapping it.

Got a screenshot?

Sent from my iPad. Please pardon typos.

On Dec 2, 2014, at 2:06 PM, "Stockly, Ed" <email@hidden> wrote:

> All the dialog says is "Stack Overflow"
>
> The dialog stays on screen with no time out forever (until someone clears it
> or restarts the machine).
>
> The dialog is owned by the applescript applet.
>
> I wonder why it's not trappable
>
>
> On 12/1/14 2:15 p.m., "Christopher Nebel" <email@hidden> wrote:
>
>> How do you know the problem is a stack overflow?  What¹s the exact text of the
>> dialog?  If it actually says ³Stack overflow², then it¹s coming from
>> AppleScript, and is ‹ or at least should be ‹ a trappable error.  (And it has
>> nothing to do with running out of VM space, so Activity Monitor or top(1)
>> won¹t help in diagnosing it.)  Why it¹s happening now and not before is a
>> bigger question.
>>
>>
>> ‹Chris N.
>>
>>> On Nov 13, 2014, at 11:24 AM, Stockly, Ed <email@hidden> wrote:
>>>
>>> So One of the machines had a stack overflow this morning and when I used UI
>>> Browser to look at the dialog, I learned that it belonged to the AppleScript
>>> applet.
>>>
>>> Every line in the script is inside an on error block, so it's not something
>>> I can trap, or use GUI scripting to clear. (I use a lot of GUI scripting
>>> with this to clear flash, java script and other dialogs as they come up.)
>>>
>>> I'm thinking I'm going to sample the memory on a regular basis and save it
>>> to log files, then, when execution is halted due to a stack overflow, I'll
>>> be able to see if anything seemed to get overloaded as the overflow
>>> approached.
>>
>>
>
>
>
> _______________________________________________
> 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

 _______________________________________________
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


  • Follow-Ups:
    • Re: Stack Overflow
      • From: "Stockly, Ed" <email@hidden>
References: 
 >Re: Stack Overflow (From: "Stockly, Ed" <email@hidden>)

  • Prev by Date: Re: Stack Overflow
  • Next by Date: RE: [rant] "Never mind the quality, feel the width!"
  • Previous by thread: Re: Stack Overflow
  • Next by thread: Re: Stack Overflow
  • Index(es):
    • Date
    • Thread