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 4019016
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T10:03:15+00:00 2026-05-20T10:03:15+00:00

I have a Thread called 10 times: [NSThread detachNewThreadSelector:@selector(workInBackground:) toTarget:self withObject:sendArray]; This is the

  • 0

I have a Thread called 10 times:

[NSThread detachNewThreadSelector:@selector(workInBackground:) toTarget:self withObject:sendArray];

This is the “workInBackground” method:

- (void)workInBackground:(NSArray*)dataArray{
    NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init]; //  create release pool
    // display dataArray sent from Main Thread
    NSLog(@"%i, %@", [[dataArray objectAtIndex:0] intValue], [dataArray objectAtIndex:1]);

    // Fetch data from URL
    NSString *myURL = [NSString stringWithFormat:@"http://somesite.com/index.php?s=%@", [dataArray objectAtIndex:1]];
    NSURL *url = [[NSURL alloc] initWithString:myURL];
    NSString *strResult = [[NSString alloc] initWithContentsOfURL:url encoding:NSUTF8StringEncoding error:nil];

    // display dataArray sent from Main Thread ... AGAIN
    NSLog(@"this will show");
    NSLog(@"%i, %@", [[dataArray objectAtIndex:0] intValue], [dataArray objectAtIndex:1]);
    NSLog(@"this will not show");

    // Code that returns super cool data to the main thread

    [pool release]; // empty pool

I’m not 100% sure that data does corrupt but I don’t understand why does the same line of code (NSLog) crash the app. I have to use data from my dataArray after the Fetch from URL but can’t.

I’m new to Objective C so I’m sorry if my error is obvious 🙂

— UPDATE — object sent to this method wasn’t retained and that was the problem!

  • 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-05-20T10:03:15+00:00Added an answer on May 20, 2026 at 10:03 am

    How do you create and manage the array sent to the background thread?

    If you have a crash, post the backtrace.


    Your workaround isn’t a fix, it is just narrowing the window of whatever race condition is killing your app.

    Best guess (lacking the code showing how the array is created) is that your array is being released by the main thread before the background thread is done with the array and strings.

    Retain the array once for each thread that is spawned and then release it in the thread when you are done with it.

    Better yet, use GCD + Blocks.

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

Sidebar

Related Questions

I have dll method that should be QoSed - this method should be called
I have a thread that needs to be executed every 10 seconds. This thread
I have a thread that appends rows to self.output and a loop that runs
In other words I have a thread that starts and calls waitHandle.Set() multiple times.
When myThread.Start(...) is called, do we have the assurance that the thread is started?
I have a function that is being called from different threads in the application.
I have thread exception handler which saves the exception stack trace and should close
Suppose I have thread 1, the main window UI thread and thread 2, a
Is if almost always required to have thread syncing (i.e. use of mutex, semaphores,
I have one thread that writes results into a Queue. In another thread (GUI),

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.