Basecamp 3.1.3 slow startup: Caused by error report

Former Member over 14 years ago

Basecamp version 3.1.3 started becoming very slow on startup -- it took up to five minutes to start.

I tracked this down to an attempt by Basecamp to process crash report information. To solve the problem I deleted the crash log files from the following directory in my Home directory:

Library/Logs/CrashReporter

I tracked this down by sampling Basecamp from my Mac's Activity Monitor. The following suspicious call appeared:

2437 glo::sendErrorReport(std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&, int, std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&)

                            2437 -[NSAppleScript executeAppleEvent:error:]

Perhaps someone at Garmin should look at this. :)

Cheers.

0 azdrmn over 14 years ago

This is indeed an issue with BaseCamp 3.1.3 that is being fixed in the upcoming 3.1.4. In the meantime, there are a couple of things that you can do to work around this. In our experience, if you open a different application, it "unhangs" BaseCamp. You can also go to $(HOME)/Library/Logs/Crash Reporter" and delete any file that starts with "BaseCamp". This will prevent the hang from occurring in the first place. Sorry for the inconvenience.