Due to a nature of Application Enhancer, it can potentially cause certain instability in your system (although, as all of you know, we work hard on preventing and/or fixing this asap).
However, many people notice traces of APE in every crash log they get (this particular post has inspired me today). In short, when an application crashes, CrashReporter dumps all the threads in the process to the crash log. One of the threads always carries __ape_agent. What is this? This is an idle thread that APE creates in the process that normally lurks idly in the background and that handles messages sent between APEs (for example, reload preferences).
While looking at the logs, you should also pay attention to the "Thread Crashed" message in one of the threads in the crash log. This is what have caused the crash, and if you see no APEBundleMain or APEBundleMessage in the trace, then it's highly unlikely an APE has caused it. If you do see one, though, please send the log to urgent at unsanity dot com - I'll investigate it immediately.
Rock on!
Posted by slava at 03:09 AM
| Comments (1)
| TrackBack (0)
Related:
- Betas, Twitter and WTF - Feb 16, 2010
- Quick Status Update - Feb 12, 2010
- It's Winter, Right? - Jan 26, 2010
- Hiya Kids, it's Theming Time! - Oct 06, 2009
- Mighty Mouse with Some Theme Sauce - Jun 02, 2009
Yeah, like I mentioned in a later post, the WSX & APE combination are working just fine now, and I suspect the stability issues might've been caused by a broken FS after a power outage. The thing is, according to several crash logs, the thread that included the "__ape_agent" (generally Thread 1) did crash. Some logs, meanwhile, displayed Thread 0 as having crashed.
Posted by: Lauri Kieksi on June 3, 2003 6:21 AM