Wednesday, January 26, 2011

Process 1018 Exceeded 500 Log Message Per Second Limit

Just found this new error code from iPhone console log:
Tue Jan 25 15:52:19 unknown App Name[1018] <Error>: *** process 1018 exceeded 500 log message per second limit  -  remaining messages this second discarded ***
Using custom log macros instead of standard NSLog(). That allows developers to leave logging calls as-in in the code, even for release version. Great! These are originally from Stack Overflow thread "NSLog tips and tricks":
#ifdef DEBUG
#   define DLog(fmt, ...) NSLog((@"%s [Line %d] " fmt), __PRETTY_FUNCTION__, __LINE__, ##__VA_ARGS__);
#   define DLog(...)

// ALog always displays output regardless of the DEBUG setting
#define ALog(fmt, ...) NSLog((@"%s [Line %d] " fmt), __PRETTY_FUNCTION__, __LINE__, ##__VA_ARGS__);
Need to start paying more attention to logging. The error mentioned above came from a customer using ad hoc debug release version, having strange problems. The problems were there even without logging, but wondering now if this too much logging will cause other problems, which wouldn't happen in normal version?

Isn't debugging fun, expecially remotely on different timezones, with nice mixture of cultural and language differencies? Really, it is fun :)

1 comment:

  1. Yes, one of the worst things that can happen is when your debugging/logging code has side-effects. Unfortunately, this happens quite often ... :-}