Home/ Questions/Q 1035771
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T14:35:43+00:00

I’m not very ‘up’ on multi-threading, but I’ve been using detachNewThreadSelector in a couple

  • 0

I’m not very ‘up’ on multi-threading, but I’ve been using detachNewThreadSelector in a couple of places to access data in a database. Unfortunately, on slower devices the first request may still be happening when I call the second… Which naturally causes a crash because both are calling the same method (which is obviously not thread-safe).

What is the best way to go about sorting a bug like this? Can I somehow queue them so that the second thread doesn’t start until the first one has finished?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You may want to have a look at NSOperation and NSOperationQueue which is an abstraction for a queue of tasks that can be run asynchronously from the main thread. If you want the NSOperationQueue to run just a NSOperation at a time (so to wait after the current task is compleate before firing the next one) you can just set the maxConcurrentOperationCount property of the queue to 1

    • 0