Simple main thread usage detector that I'm using in PSPDFKit to find performance problems early on.

gistfile1.m

// Smart little helper to find main thread hangs. Enable in appDidFinishLaunching.
// Only available with source code in DEBUG mode.
@interface PSPDFHangDetector : NSObject
+ (void)startHangDetector;
@end


@implementation PSPDFHangDetector
+ (void)startHangDetector {
#ifdef DEBUG
    NSThread *hangDetectionThread = [[NSThread alloc] initWithTarget:self selector:@selector(deadThreadMain) object:nil];
    [hangDetectionThread start];
#endif
}

#ifdef DEBUG
static volatile NSInteger DEAD_SIGNAL = 0;
+ (void)deadThreadTick {
    if (DEAD_SIGNAL == 1) {
        NSLog(@"Main Thread doesn't answer...");
    }
    DEAD_SIGNAL = 1;
    dispatch_async(dispatch_get_main_queue(), ^{DEAD_SIGNAL = 0;});
}

+ (void)deadThreadMain {
    [NSThread currentThread].name = @"PSPDFHangDetection";
    @autoreleasepool {
        [NSTimer scheduledTimerWithTimeInterval:0.5 target:self selector:@selector(deadThreadTick) userInfo:nil repeats:YES];
        [[NSRunLoop currentRunLoop] runUntilDate:[NSDate distantFuture]];
    }
}
#endif

@end

I am trying to make this usable as part of HockeySDK (for beta versions), but running into some issues. The goal is to have a flag set in a file which tells the app that the last time it ended, the main thread was blocked and try to make this as bullet proof as possible.

1. The background thread continues to run once the app goes into background. Which will cause the watchdog to jump in after 10 seconds, because the app runs in the background for longer than it is allowed (default behavior). It would crash (watchdog doesn't kill an app after startup if it blocks the main thread), but the reason is different than the intend is, so this is not wanted.
2. To solve this I would change this to just GCD and when going into background or terminate it would release the background queue.
3. But if the main thread is blocked (e.g. endless loop), the app won't be notified that it is going to background, since that is all handled by UIKit in the main thread only.
4. To solve this I would stop the ticket in the background queue, after the main thread did not answer the first time.
5. Now it could happen that the app just stalled for some time, which is a little longer than the ticker interval. So another "ticker" should then started on the main thread which would restart the background ticker in this case.

Any ideas or does that sound feasible to you?