Thank you Dave, disabling ReportCrash as your link shows, works like a champ!
On Mon, Nov 9, 2009 at 5:03 PM, Dave MacLachlan <dmacl...@google.com> wrote: > > On Nov 9, 2009, at 4:57 PM, Eric Roman wrote: > >> >> Whenever I hit a CHECK/DCHECK in the chrome unit tests on mac, >> after printing a backtrace (which btw lacks the symbol names), >> the process locks up and becomes un-killable! >> >> It won't respond to either SIGINT or SIGKILL. >> >> It looks like the villain is the ReportCrash process. >> >> As this is happening, ReportCrash happily chews up 100% CPU for about >> 5-10 minutes. >> >> I confirmed ReportCrash is the villain, since if I murder it as root >> then the unit-test is killed right away. >> >> I don't know what is going on with ReportCrash, but it is certainly >> very frustrating. >> >> Running fs_usage I notice that ReportCrash is repeatedly >> open/close/fstate the same *.a files under src/xcodebuild/Debug. >> So my guess is that ReportCrash is having a heart attack trying to >> symbolicate. >> >> Anyone know how to fix this? >> Can I disable ReportCrash if not? >> >> Thanks! >> >> /me is a mac n00b so please be gentle :) >> > > Give this a shot... I think it will do it for you. > > http://www.macosxhints.com/article.php?story=20090902164105138 > > I haven't looked into it, but I'm assuming the reason it's so slow is > because of the bad DSYM parsing in Leopard. It should be much faster in Snow > Leopard, but that probably doesn't help you. > > Cheers, > Dave > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
