I have developed a Cocoa app which fetches text from an InCopy document via AppleEvents through a plugin in InCopy, and sends the text to a server for text proofing. This application have performed well in different environments the last year, but one of our customers had problems with the application suddenly stops working.
When debugging the cocoa app, I found that it works well for the same InCopy document in about 9 out of 10 runs. But when it fails for the 10th time, it is always after having sent a soap request to the server. It polls the server by sending a request, and waiting for a reply. When it fails, the application doesn't work any longer. The actions behind the buttons doesn't get executed, but the buttons does highlight. No NSLog lines are sent to the console any more, even though there is a timer that should send an NSLog message every second. The application doesn't crash, because when I quit InCopy, the application is sent a quit AppleScript message through Finder, and it quits without any problem. And then it works again when started up until next time it fails. I got the OS X reinstalled on the machine, with Leopard 10.5.8, but the same thing happens again. The only abnormal thing I can see from the console, is that when InCopy starts up, I get messages like: Jul 22 11:16:53 AAA-test1-eng-news-d /Library/Application Support/FLEXnet Publisher/Service/11.5.0/FNPLicensingService[161]: Started - This service performs licensing functions on behalf of FLEXnet enabled products. and then about every 20 seconds I get Jul 22 11:16:53 AAA-test1-eng-news-d kernel[0]: unknown SIGSEGV code 0 Jul 22 11:17:23: --- last message repeated 77 times --- Jul 22 11:17:33 AAA-test1-eng-news-d kernel[0]: unknown SIGSEGV code 0 Jul 22 11:18:03: --- last message repeated 3 times --- Jul 22 11:18:13 AAA-test1-eng-news-d kernel[0]: unknown SIGSEGV code 0 Jul 22 11:18:43: --- last message repeated 3 times --- I suspect that this can have something to do with my application failing. But running the same application from Xcode on the same machine, it performs flawlessly. I have tried for a couple of weeks now to find out why my application fails, but have not come any closer to a solution. If we doesn't get this solved, we lose a customer, so it is very important for us to find a solution. Does anyone have any hint to give me? Ivan _______________________________________________ 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
