Sometimes when I quit my AppleScript Studio app it crashes and I get the following error:
MyApp has exited due to signal 11 (SIGSEGV).
I can’t figure out what this means but I have managed to narrow down when it happens. It only occurs when you customize the toolbar in my app. All other times my application exits with status 0 (normal). However, anytime you click on customize toolbar, even if you don’t do anything, the app will run fine until you try to quit, and then it will crash. Does anyone have any ideas about this?
ps. I can run the Simple Toolbar project that is in the AppleScript Studio examples folder just fine. It never crashes after customize toolbar. Is my project just corrupted or something?
Apparently this is just an issue with a corrupted project. I’m not sure exactly what part is corrupted, but if I copy and paste just the toolbar code into a new project, the problem disappears. Hopefully if I transfer over the rest of my app and its user interface to the new project as well, the problem won’t come back.
A rather late reply, but perhaps it’s of some use to others: doing a clean build (xcode >> menu Build >> Clean) often does the trick as well. SIGSEGV is Unix-speak for “don’t understand”. The Clean command sorts out the stuff that goes on behind the screens of an xcode project.
I ran across this same problem (please refer to a more recent thread: Quit from AS Studio application) and have been in a quandary ever since what to do, short of moving all buttons and windows to a fresh new project. I tried the suggestion to do a clean build several times but the problem hasn’t budged a bit.
I also get the SIGSEGV error message but also have new ones as follows:
-application has exited due to signal 10 (SIGBUS).
-applescript error -1762
Any new solution possible? Or leads on what these messages might mean that would help me track the problems and get them fixed?
I truly abhor transplanting the entire IB to a new project and starting all over again. How I wish Apple would provide an easier way to to this. Or is there already?
TIA for new tips and/or leads that would help me fix this problem.
Here’s a quick update - following a painstaking bug hunt which finally solved my problem with quit and thus, with the inability of my app to preserve preferred settings.
I noted that some of my windows had “Released when closed” inadvertently activated which caused the trouble with missing components that the application needs when quitting. Unchecking this option in the IB for my windows wonders for me. Now, I’ve got my app working flawlessly (hmm…perhaps until some other bug surfaces…I hope not).
I hope this tip works for those who might need it.
It seems like this is a much more acute problem than just “quit” from AS Studio application that is related when with the upgrade to OS 10.4.3. It seems that even upgrading to 10.4.4 brought the same problems over for me.
Please refer to another thread in this forum entitled “10.4.3 breakage” by deanshavit.
