RE: Application crashes after launching Open/Save dialogs

[Michael Domino]

Sanyam,

FYI, I had a similar problem with an accessory view that was crashing  
until I added this line:


[dirDlg setAccessoryView:nil];	// On Snow Leopard, we need to do this  
or we will subsequently crash.


-Michael Domino

Michael Domino | Identity Finder, LLC
250 West 57th St; Suite 2412 | New York, NY 10107
P: 617-816-5851 | F: 888-206-6389 | E: michael.dom...@identityfinder.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Application crashes after launching Open/Save dialogs

[Kyle Sluder]

On Thu, Aug 11, 2011 at 10:35 PM, Sanyam Jain  wrote:
> Still I was wondering, System should not have send some message to the 
> delegate once the dialog is dismissed.
> That's strange behavior.

It's quite common, and something the documentation explicitly calls
out. See the last paragraph of "Use Weak References to Avoid Retain
Cycles" in the Memory Management Programming Guide:
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/MemoryMgmt/Articles/mmPractical.html#//apple_ref/doc/uid/TP40004447-1000810

--Kyle Sluder
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

RE: Application crashes after launching Open/Save dialogs

[Sanyam Jain]

Thanks a lot for the reply.
I was able to figure out the problem.
I was doing following sequence of things -

-  NSOpenPanel* openPanelRef = [[NSOpenPanel alloc] init]; // created 
an instance of open panel

-  MyCustomDelegate* openPanelDelegate = [[MyCustomDelegate alloc] 
init]; // created instance of custom delegate

-  [openPanelRef setDelegate : openPanelDelegate]; // attached as a 
delegate

-  [openPanelRef runModal]; // ran the modal open dialog

-  // Missed something here

-  [openPanelRef release];

-  [openPanelDelegate release];


-  After all the open stuff, whenever I open any other window, 
application used to crash.


The fix was placing [openPanelRef setDelegate: nil]; in the "//Missed something 
here".

Still I was wondering, System should not have send some message to the delegate 
once the dialog is dismissed.
That's strange behavior.

-Sanyam

From: Jens Alfke [mailto:j...@mooseyard.com]
Sent: Friday, August 12, 2011 9:20 AM
To: Sanyam Jain
Cc: cocoa-dev@lists.apple.com
Subject: Re: Application crashes after launching Open/Save dialogs


On Aug 8, 2011, at 2:34 AM, Sanyam Jain wrote:


Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib  0x92dd3eec objc_msgSend + 44


A crash in objc_msgsend means a message was sent to a bad object pointer. 
Usually this means the object has already been dealloced and so its memory is 
garbage. (You can read up on NSZombieEnabled in the docs, for a general 
technique to debug this.)


2   com.apple.CoreFoundation   0x93c4e793 __CFXNotificationPost 
+ 947
3   com.apple.CoreFoundation   0x93c4e19a 
_CFXNotificationPostNotification + 186


>From this you can deduce that a notification is being delivered. So what's 
>going on is that one of your objects registered for NSNotifications, but 
>forgot to remove itself as an observer in its -dealloc method, so the 
>NSNotificationCenter still has a dangling pointer to it.

11  com.apple.Foundation  0x918ad669 -[NSNotificationCenter 
postNotificationName:object:] + 56
12  com.apple.AppKit 0x93ea151a -[NSTableView 
_enableSelectionPostingAndPost] + 509
13  com.apple.AppKit 0x93eacc17 -[NSTableView 
selectRowIndexes:byExtendingSelection:] + 168

...And from this, it looks like the notification is posted because a table 
view's selection changed.

>From this you ought to be able to figure out what class the bug is in and fix 
>it. The rule of thumb is that in ANY class where you register self as an 
>observer with an NSNotificationCenter, you MUST remove self as an observer in 
>the -dealloc method.

-Jens
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Application crashes after launching Open/Save dialogs

[Jens Alfke]

On Aug 8, 2011, at 2:34 AM, Sanyam Jain wrote:

> Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
> 0   libobjc.A.dylib  0x92dd3eec objc_msgSend + 44

A crash in objc_msgsend means a message was sent to a bad object pointer. 
Usually this means the object has already been dealloced and so its memory is 
garbage. (You can read up on NSZombieEnabled in the docs, for a general 
technique to debug this.)

> 2   com.apple.CoreFoundation   0x93c4e793 
> __CFXNotificationPost + 947
> 3   com.apple.CoreFoundation   0x93c4e19a 
> _CFXNotificationPostNotification + 186

From this you can deduce that a notification is being delivered. So what’s 
going on is that one of your objects registered for NSNotifications, but forgot 
to remove itself as an observer in its -dealloc method, so the 
NSNotificationCenter still has a dangling pointer to it.

> 11  com.apple.Foundation  0x918ad669 -[NSNotificationCenter 
> postNotificationName:object:] + 56
> 12  com.apple.AppKit 0x93ea151a -[NSTableView 
> _enableSelectionPostingAndPost] + 509
> 13  com.apple.AppKit 0x93eacc17 -[NSTableView 
> selectRowIndexes:byExtendingSelection:] + 168

…And from this, it looks like the notification is posted because a table view’s 
selection changed.

From this you ought to be able to figure out what class the bug is in and fix 
it. The rule of thumb is that in ANY class where you register self as an 
observer with an NSNotificationCenter, you MUST remove self as an observer in 
the -dealloc method.

—Jens

smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Application crashes after launching Open/Save dialogs

[Sanyam Jain]

Hi,

I have a Carbon based application, in which platform Open/save dialogs are 
based on NSOpenPanel and NSSavePanel.
Since, am accessing Cocoa stuff inside Carbon app, I did NSApplicationLoad() as 
suggested in one of Apple's document.

Whenever another dialog window is launched after the Open/Save dialog, 
application crashes.

Following is the crash log -
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xffc6c6c6
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Application Specific Information:
objc_msgSend() selector name: respondsToSelector:

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib  0x92dd3eec objc_msgSend + 44
1   com.apple.Foundation 0x918ab3bf _nsnote_callback + 176
2   com.apple.CoreFoundation   0x93c4e793 __CFXNotificationPost 
+ 947
3   com.apple.CoreFoundation   0x93c4e19a 
_CFXNotificationPostNotification + 186
4   com.apple.Foundation 0x918a025c -[NSNotificationCenter 
postNotificationName:object:userInfo:] + 128
5   com.apple.Foundation 0x918ad669 -[NSNotificationCenter 
postNotificationName:object:] + 56
6   com.apple.AppKit  0x94297afb -[NSNavView 
_handleSelectionChanged] + 73
7   com.apple.Foundation 0x918ab3bf _nsnote_callback + 176
8   com.apple.CoreFoundation   0x93c4e793 __CFXNotificationPost 
+ 947
9   com.apple.CoreFoundation   0x93c4e19a 
_CFXNotificationPostNotification + 186
10  com.apple.Foundation  0x918a025c -[NSNotificationCenter 
postNotificationName:object:userInfo:] + 128
11  com.apple.Foundation  0x918ad669 -[NSNotificationCenter 
postNotificationName:object:] + 56
12  com.apple.AppKit 0x93ea151a -[NSTableView 
_enableSelectionPostingAndPost] + 509
13  com.apple.AppKit 0x93eacc17 -[NSTableView 
selectRowIndexes:byExtendingSelection:] + 168
14  com.apple.AppKit 0x9428f104 -[NSNavOutlineDelegate 
_setHighlightedRowsFromNodes:maintainFirstVisibleRow:] + 252
15  com.apple.AppKit 0x9428e07c -[NSNavOutlineDelegate 
reloadChildrenForNode:] + 160
16  com.apple.AppKit 0x94276279 -[NSNavDataSource 
_reloadChildrenForNode:] + 67
17  com.apple.AppKit 0x9427467e -[NSNavDataSource 
_handleAddedChildNode:toExpandedNode:] + 144
18  com.apple.AppKit 0x9427af5c -[NSNavDataSource 
observeValueForKeyPath:ofObject:change:context:] + 845
19  com.apple.AppKit 0x9427dea4 -[NSNavFBENode 
_sendChildrenChangedWithDictionary:] + 501
20  com.apple.AppKit 0x9428261e NSNavNodeEventHandler + 1433
21  com.apple.CoreFoundation  0x93c32361 __CFRunLoopDoSources0 
+ 1201
22  com.apple.CoreFoundation  0x93c2ff8f __CFRunLoopRun + 1071
23  com.apple.CoreFoundation  0x93c2f464 CFRunLoopRunSpecific + 
452
24  com.apple.CoreFoundation  0x93c2f291 CFRunLoopRunInMode + 97
25  com.apple.HIToolbox  0x938f8e04 RunCurrentEventLoopInMode + 392
26  com.apple.HIToolbox  0x938f8bb9 ReceiveNextEventCommon + 354
27  com.apple.HIToolbox  0x93a81137 ReceiveNextEvent + 83


Are there other pre-configuration steps before calling Cocoa calls from Carbon 
app?
Please provide your suggestions on the possible cause of crash.

- Sanyam

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Application crashes with no calls tracing back to my code

[Arun]

I fixed the crash.
I had to use GuardMalloc.

Thanks all for the suggestions.

-Arun

On Sat, Mar 27, 2010 at 5:40 PM, Ken Thomases  wrote:

> On Mar 27, 2010, at 7:00 AM, Ken Thomases wrote:
>
> > On Mar 27, 2010, at 6:29 AM, Arun wrote:
> >
> >> My application is crashing sometimes with the following crash log. It
> has no
> >> traces of my code. Can anyone look into the crash log suggest some
> ideas?
> >
> > Probably a memory management bug.  You are over-releasing or
> under-retaining something.  An NSImage, from the looks of things.
> >
> >
> http://www.sealiesoftware.com/blog/archive/2008/09/22/objc_explain_So_you_crashed_in_objc_msgSend.html
>
> And beyond the advice at the link, I should have said to use the Zombie
> instrument or, the manual way, set NSZombieEnabled=YES and
> MallocStackLoggingNoCompact=YES, set a breakpoint in -[_NSZombie
> methodSignatureForSelector:], then when the debugger stops on that
> breakpoint, use "info malloc-history" command to figure out where the zombie
> was originally allocated.
>
>
> http://www.friday.com/bbum/2010/01/10/using-malloc-to-debug-memory-misuse-in-cocoa/
> http://developer.apple.com/mac/library/technotes/tn2004/tn2124.html
>
> Also, use Xcode's Build and Analyze feature to see if the static analyzer
> can identify your memory management bugs.
>
> Cheers,
> Ken
>
>
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Application crashes with no calls tracing back to my code

[Ken Thomases]

On Mar 27, 2010, at 7:00 AM, Ken Thomases wrote:

> On Mar 27, 2010, at 6:29 AM, Arun wrote:
> 
>> My application is crashing sometimes with the following crash log. It has no
>> traces of my code. Can anyone look into the crash log suggest some ideas?
> 
> Probably a memory management bug.  You are over-releasing or under-retaining 
> something.  An NSImage, from the looks of things.
> 
> http://www.sealiesoftware.com/blog/archive/2008/09/22/objc_explain_So_you_crashed_in_objc_msgSend.html

And beyond the advice at the link, I should have said to use the Zombie 
instrument or, the manual way, set NSZombieEnabled=YES and 
MallocStackLoggingNoCompact=YES, set a breakpoint in -[_NSZombie 
methodSignatureForSelector:], then when the debugger stops on that breakpoint, 
use "info malloc-history" command to figure out where the zombie was originally 
allocated.

http://www.friday.com/bbum/2010/01/10/using-malloc-to-debug-memory-misuse-in-cocoa/
http://developer.apple.com/mac/library/technotes/tn2004/tn2124.html

Also, use Xcode's Build and Analyze feature to see if the static analyzer can 
identify your memory management bugs.

Cheers,
Ken

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Application crashes with no calls tracing back to my code

[Roland King]

And by the way this question, or basically this question, comes up 2-3 times a 
week, every week. 

If you checked the archives you would have found many suggestions about how to 
find this. 

On 27-Mar-2010, at 8:00 PM, Ken Thomases wrote:

> On Mar 27, 2010, at 6:29 AM, Arun wrote:
> 
>> My application is crashing sometimes with the following crash log. It has no
>> traces of my code. Can anyone look into the crash log suggest some ideas?
> 
> Probably a memory management bug.  You are over-releasing or under-retaining 
> something.  An NSImage, from the looks of things.
> 
> http://www.sealiesoftware.com/blog/archive/2008/09/22/objc_explain_So_you_crashed_in_objc_msgSend.html
> 
> Regards,
> Ken
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
> 
> This email sent to r...@rols.org

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Application crashes with no calls tracing back to my code

[Ken Thomases]

On Mar 27, 2010, at 6:29 AM, Arun wrote:

> My application is crashing sometimes with the following crash log. It has no
> traces of my code. Can anyone look into the crash log suggest some ideas?

Probably a memory management bug.  You are over-releasing or under-retaining 
something.  An NSImage, from the looks of things.

http://www.sealiesoftware.com/blog/archive/2008/09/22/objc_explain_So_you_crashed_in_objc_msgSend.html

Regards,
Ken

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Application crashes with no calls tracing back to my code

[Arun]

Hi All,
My application is crashing sometimes with the following crash log. It has no
traces of my code. Can anyone look into the crash log suggest some ideas?

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x2098d5e8
Crashed Thread:  0

Thread 0 Crashed:
0   libobjc.A.dylib   0x93c9e699 objc_msgSend + 41
1   com.apple.AppKit   0x94ec60aa _NSBitmapImageRepFromImage +
35
2   com.apple.AppKit   0x9525004b
-[NSImageCell(NSPrivateAnimationSupport) _animationTimerCallback:] + 52
3   com.apple.Foundation   0x903aa1e3 __NSFireTimer + 147
4   com.apple.CoreFoundation   0x9242fb45 CFRunLoopRunSpecific + 4469
5   com.apple.CoreFoundation   0x9242fcf8 CFRunLoopRunInMode + 88
6   com.apple.HIToolbox   0x968a9480 RunCurrentEventLoopInMode + 283
7   com.apple.HIToolbox   0x968a9299 ReceiveNextEventCommon + 374
8   com.apple.HIToolbox   0x968a910d
BlockUntilNextEventMatchingListInMode + 106
9   com.apple.AppKit   0x94db53ed _DPSNextEvent + 657
10  com.apple.AppKit   0x94db4ca0 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
11  com.apple.AppKit   0x94dadcdb -[NSApplication run] + 795
12  com.apple.AppKit   0x94d7af14 NSApplicationMain + 574
13  com.yourcompany.Vi2   0x218e start + 54

Thread 1:
0   libSystem.B.dylib 0x908554a6 mach_msg_trap + 10
1   libSystem.B.dylib 0x9085cc9c mach_msg + 72
2   com.apple.CoreFoundation   0x9242f0ce CFRunLoopRunSpecific + 1790
3   com.apple.CoreFoundation   0x9242fcf8 CFRunLoopRunInMode + 88
4   com.apple.CFNetwork   0x92d98eca CFURLCacheWorkerThread(void*) +
396
5   libSystem.B.dylib 0x908866f5 _pthread_start + 321
6   libSystem.B.dylib 0x908865b2 thread_start + 34

Thread 2:
0   libSystem.B.dylib 0x9085c68e __semwait_signal + 10
1   libSystem.B.dylib 0x908b2c59 sleep$UNIX2003 + 63
2   com.yourcompany.Vi2   0xaa28 -[SubTask1Handler
performActivation] + 208 (SubTask1Handler.mm:179)
3   com.yourcompany.Vi2   0xa795 -[SubTask1Handler
performSubTask:] + 403 (SubTask1Handler.mm:101)
4   com.yourcompany.Vi2   0x3e4b -[MainWindowController
processSubTask1:] + 133 (MainWindowController.mm:952)
5   com.yourcompany.Vi2   0x3815 -[MainWindowController
readConfiguration] + 757 (MainWindowController.mm:758)
6   com.apple.Foundation   0x90375bad -[NSThread main] + 45
7   com.apple.Foundation   0x90375754 __NSThread__main__ + 308
8   libSystem.B.dylib 0x908866f5 _pthread_start + 321
9   libSystem.B.dylib 0x908865b2 thread_start + 34

Thread 3:
0   libSystem.B.dylib 0x908554a6 mach_msg_trap + 10
1   libSystem.B.dylib 0x9085cc9c mach_msg + 72
2   com.apple.CoreFoundation   0x9242f0ce CFRunLoopRunSpecific + 1790
3   com.apple.CoreFoundation   0x9242fcf8 CFRunLoopRunInMode + 88
4   com.apple.Foundation   0x903d9100
+[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5   com.apple.Foundation   0x90375bad -[NSThread main] + 45
6   com.apple.Foundation   0x90375754 __NSThread__main__ + 308
7   libSystem.B.dylib 0x908866f5 _pthread_start + 321
8   libSystem.B.dylib 0x908865b2 thread_start + 34



Thanks
Arun KA
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Application crashes

[Sean McBride]

On 1/19/10 6:34 PM, yogin bhargava said:

>HI All,
>  I have a cocoa application. Rarely it crashes with the following log
>crash messages :
>
>Thread 0 Crashed:
>0   libobjc.A.dylib   0x93960699 objc_msgSend + 41

Have you read this:


--

Sean McBride, B. Eng s...@rogue-research.com
Rogue Researchwww.rogue-research.com
Mac Software Developer  Montréal, Québec, Canada


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Application crashes

[Joar Wingfors]

Yogin,

It seems very likely that the target for your timer (the object that would 
receive the delayed method call) has been deallocated. I would use zombies to 
figure out why that is. You can use them either from Xcode, or via Instruments. 
Google has more info.

j o a r


On 19 jan 2010, at 05.04, yogin bhargava wrote:

> HI All,
>  I have a cocoa application. Rarely it crashes with the following log
> crash messages :
> 
> Thread 0 Crashed:
> 0   libobjc.A.dylib   0x93960699 objc_msgSend + 41
> 1   com.apple.Foundation   0x90ecf483 __NSFireTimer + 147
> 2   com.apple.CoreFoundation   0x918108f5 CFRunLoopRunSpecific + 4469
> 3   com.apple.CoreFoundation   0x91810aa8 CFRunLoopRunInMode + 88
> 4   com.apple.HIToolbox   0x952302ac RunCurrentEventLoopInMode + 283
> 5   com.apple.HIToolbox   0x952300c5 ReceiveNextEventCommon + 374
> 6   com.apple.HIToolbox   0x9522ff39
> BlockUntilNextEventMatchingListInMode + 106
> 7   com.apple.AppKit   0x9468e6d5 _DPSNextEvent + 657
> 8   com.apple.AppKit   0x9468df88 -[NSApplication
> nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
> 9   com.apple.AppKit   0x94686f9f -[NSApplication run] + 795
> 10  com.apple.AppKit   0x946541d8 NSApplicationMain + 574
> 11  com.yourcompany.Vi2   0x23f2 start + 54
> 
> Does anybody have an idea of what could be going wrong.
> 
> Thanks in advance.
> YOGIN

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Application crashes

[yogin bhargava]

HI All,
  I have a cocoa application. Rarely it crashes with the following log
crash messages :

Thread 0 Crashed:
0   libobjc.A.dylib   0x93960699 objc_msgSend + 41
1   com.apple.Foundation   0x90ecf483 __NSFireTimer + 147
2   com.apple.CoreFoundation   0x918108f5 CFRunLoopRunSpecific + 4469
3   com.apple.CoreFoundation   0x91810aa8 CFRunLoopRunInMode + 88
4   com.apple.HIToolbox   0x952302ac RunCurrentEventLoopInMode + 283
5   com.apple.HIToolbox   0x952300c5 ReceiveNextEventCommon + 374
6   com.apple.HIToolbox   0x9522ff39
BlockUntilNextEventMatchingListInMode + 106
7   com.apple.AppKit   0x9468e6d5 _DPSNextEvent + 657
8   com.apple.AppKit   0x9468df88 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
9   com.apple.AppKit   0x94686f9f -[NSApplication run] + 795
10  com.apple.AppKit   0x946541d8 NSApplicationMain + 574
11  com.yourcompany.Vi2   0x23f2 start + 54

Does anybody have an idea of what could be going wrong.

Thanks in advance.
YOGIN
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com