BaseCamp 3.2.1 startup crashes?

I removed the City Navigator North America NT 2010.10 map from the app support/Garmin/maps folder and it still crashed.

Here's the log, and thank you for the much more efficiant way to get to the hidden Library. :D

Maps can be stored in two locations:
/Library/Application Support/Garmin/Maps/
and
/Users/{username}/Library/Application Support/Garmin/Maps/

Please be sure to check both.

Maps can be stored in two locations:
/Library/Application Support/Garmin/Maps/
and
/Users/{username}/Library/Application Support/Garmin/Maps/

Please be sure to check both.

OK, looks like I had 24kb of a TOPO U.S. 24K North Central v2 file hidden away in the /Library/Application Support/Garmin/Maps/ location, BaseCamp now starts up! :D

Thank you!

OK, looks like I had 24kb of a TOPO U.S. 24K North Central v2 file hidden away in the /Library/Application Support/Garmin/Maps/ location, BaseCamp now starts up! :D

Thank you!

So it appears you had a partially downloaded map living in your map directory. Please send us that partial file to [email][email protected][/email] so that we can look into patching BaseCamp to not crash with a partial map installed.

I
Here's a way to try to fix this situation in 3.2.1:
Delete the file YourUsername/Library/Preferences/com.garmin.basecamp.plist . This will result in losing your preferences data, but your user data will be safe.

This worked for me as well as deleting a map file that I installed before the problem started.

I have a disk from Garmin with the 24k map and the original version of Basecamp beta. So far after 5 attempts, it upgrades twice. The final upgrade is to 3.21 and it crashes at startup.

When i look in the Library/Garmin I have no MAP folder.

I will uninstall again and reinstall and upgrade to 2.1 and it will work. Cant seem to get past that.

I also tried installing 3.21 directly from Garmin website and had the same crash at startup.

3.2.1 non-startup crash

submitted this earlier through the automatic mac error reporting dialog that popped up after the crash:
Renamed a track to from 'Active Log 00n 00m' to 20110702-HHMM,
hit enter,
and it crashed.

I had previously renamed several tracks in a similar manner.

Additional info:
this track was in a 'last 35 days' 'smart list' when I started BC at 8am this morning.
When I tried renaming, it it no longer was (track start time was 9:12am).

I am sure I had switched through various collections/lists in the mean time, even created two new ones. Does that smart list only get updated at startup?

THELIGHTGUY:

It seems this crash is due to a map product. If you could remove maps from your Library/Garmin/Maps folder one at a time (just drag them into another folder so you don't lose them) and pay attention to which one you have to remove to make BaseCamp launch successfully, I'd be curious to know which map we're having problems with.

Yes, this was the problem for me. It was the MetroGuide North America v8 that caused the problem. Take it out of the Maps folder: no crash. Put it back: crash on startup.

crash after crash after crash

Have tried deleting the plist file mentioned, still crashes. Tried looking for a map file in both library locations, one not found.

First time I started up 3.2.1 and used my Garmin Oregon 550t for the first time it pulled the maps in from the Oregon just fine. Now when I try to open it tho, crash after crash after crash. :mad:

Have you tried a master reset on the Oregon?

DSHILLIS:

I'd guess that this has something to do with your user data, probably a track you received from your Oregon, duplicated, and then edited. You could "fix" this by renaming your /Users/USERNAME/Library/Application Support/Garmin/BaseCamp folder, but that'll result in data loss.

We've got a fix incoming, but it's likely that you've already damaged some recently duplicated/edited track data if you're experiencing this issue. Generally, damaged tracks will still be there, but much of their track point data (timestamps, temperatures, etc.) will be gone. Sorry about that :(.

The next version of BaseCamp should start up with corrupted tracks without needing to rename your whole data folder, so you may want to wait for that.