Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8834473
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T09:01:30+00:00 2026-06-14T09:01:30+00:00

App crashes with error Thread 1: signal SIGKILL when I start it up the

  • 0

App crashes with error “Thread 1: signal SIGKILL” when I start it up the second time in the simulator. The first time it will work perfectly, but if I close the app completely (double tapping the home button and closing the app) and start it up again – it crashes.

I found others having the same problem (app crashes second time), but not of the same cause.

I tried creating a new project to isolate the error, and it happens when I’m trying to programmatically load a ViewController.

I have made two simple classes: MainView and Loader (which is supposed to load MainView).

In the viewDidAppear method in the Loader class I have the following code:

[super viewDidAppear:YES];

sleep(1); //Simulating to be doing stuff
MainView* mainView = [self.storyboard instantiateViewControllerWithIdentifier:@"MainView"];
[self presentViewController:mainView animated:YES completion:nil];

I get the following backtrace:

* thread #1: tid = 0x1f03, 0x9b5f5c22 libsystem_kernel.dylib`mach_msg_trap + 10, stop reason = signal SIGKILL
frame #0: 0x9b5f5c22 libsystem_kernel.dylib`mach_msg_trap + 10
frame #1: 0x9b5f51f6 libsystem_kernel.dylib`mach_msg + 70
frame #2: 0x0139b10a CoreFoundation`__CFRunLoopServiceMachPort + 186
frame #3: 0x012fe550 CoreFoundation`__CFRunLoopRun + 1312
frame #4: 0x012fdd84 CoreFoundation`CFRunLoopRunSpecific + 212
frame #5: 0x012fdc9b CoreFoundation`CFRunLoopRunInMode + 123
frame #6: 0x012b07d8 GraphicsServices`GSEventRunModal + 190
frame #7: 0x012b088a GraphicsServices`GSEventRun + 103
frame #8: 0x00011626 UIKit`UIApplicationMain + 1163
frame #9: 0x00001c4d progLoadingTest`main + 141 at main.m:16
frame #0: 0x9b5f5c22 libsystem_kernel.dylib`mach_msg_trap + 10
frame #1: 0x9b5f51f6 libsystem_kernel.dylib`mach_msg + 70
frame #2: 0x0139b10a CoreFoundation`__CFRunLoopServiceMachPort + 186
frame #3: 0x012fe550 CoreFoundation`__CFRunLoopRun + 1312
frame #4: 0x012fdd84 CoreFoundation`CFRunLoopRunSpecific + 212
frame #5: 0x012fdc9b CoreFoundation`CFRunLoopRunInMode + 123
frame #6: 0x012b07d8 GraphicsServices`GSEventRunModal + 190
frame #7: 0x012b088a GraphicsServices`GSEventRun + 103
frame #8: 0x00011626 UIKit`UIApplicationMain + 1163
frame #9: 0x00001c4d progLoadingTest`main + 141 at main.m:16
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T09:01:31+00:00Added an answer on June 14, 2026 at 9:01 am

    I found out that this is normal behavior for any app that you close in the emulator and then start again in the emulator. I just coincidentally happened to be loading a ViewController. As such it really is not a crash.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

My app crashes every time I start it in the emulator. Here is the
I'm trying to create layout inflater, but app crashes and gives NullException error in
My app crashes several times without any error or stack trace on my console.
my app crashes with this code.. it doesnt even start up.. any ideas guys
I've started using the CAGradientLayer but my app crashes CAGradientLayer *gradient = [CAGradientLayer layer];
I have an app that works on iPhone simulator but not on iPhone target
My prototype android app (I should mention it's my first) crashes whenever I run
Instruments.app crashes when I try to profile on the device. It works fine in
my app crashes often in this for-loop: for (int a = 0; a <=
my app crashes when the user tries to delete a row from the UITableView

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.