BaseCamp 3.2.1 startup crashes?

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.

I have too much valuable data to lose, so that option doesn't work. I'll just have to hang out and wait until a patch comes out. If you want me to test something, please feel free to send it my way!

Crashed due to track data

I kept crashing Basecamp after I downloaded tracks from my Gpsmap 60 CSx. I am running Mac OS 10.6.8 and Basecamp 3.2.1. I had never had crashes of this type before. I think the crashes started with my first download of tracks to Basecamp 3.2.1.

After a lot of reading of forums and stumbling around I found that I could get Basecamp to work of I removed the Alldata.gdb and Alldata.gdb.bak files. I got a few error messages but st least Basecamp seems to work.

Now the problem is how to recover the data in my saved copies of the Alldata files that contain my tracks etc. Any help recovering my old dat and reinserting it in Basdecamp?

3.2.2 should fix the issue where duplicating and editing tracks can corrupt track data and cause BaseCamp to fail at startup. You may have lost some track data (geo position data is safe, but other info like time and temperature are vulnerable to this bug). "Fortunately" the app stopped loading successfully the first time a track got corrupted in this way, so it will be rare for someone to lose more than one-BaseCamp-run of recently edited track data, and if you've still got it on your device you can restore it from there.

For people still on 3.2.1: The data causing this crash is living in your Garmin/Basecamp/Database/3.2/TrackSegments folder. Blasting your gdb/gfi files will keep us from looking up those files, and thus "fixes" the situation, but upgrading to 3.2.2 is both safer and will keep future track edits from causing this issue.

3.2.2 should fix the issue where duplicating and editing tracks can corrupt track data and cause BaseCamp to fail at startup. You may have lost some track data (geo position data is safe, but other info like time and temperature are vulnerable to this bug). "Fortunately" the app stopped loading successfully the first time a track got corrupted in this way, so it will be rare for someone to lose more than one-BaseCamp-run of recently edited track data, and if you've still got it on your device you can restore it from there.

For people still on 3.2.1: The data causing this crash is living in your Garmin/Basecamp/Database/3.2/TrackSegments folder. Blasting your gdb/gfi files will keep us from looking up those files, and thus "fixes" the situation, but upgrading to 3.2.2 is both safer and will keep future track edits from causing this issue.

PAXTER1, is there any way you can help me to not lose my data? It isn't a lot, but it is very important, I really need it.

Have you tried the suggested route? You can always manually back up your BaseCamp folder just in case it has problems, and it should recover as much as can be recovered. The most data you could lose would be non-geolocation data for tracks you duplicated in 3.2.1.

The only alternative I can think of is that if you had this data in 3.1, you can instead just rename your ~/Library/Application Support/Garmin/BaseCamp/Database/3.2 folder to something like "My New Data" so BaseCamp can't find it and loads that older data instead. Then you can export your old 3.1tracks to GPX, name your Database/3.2 folder correctly again, and restart and import said GPX file.

Have you tried the suggested route? You can always manually back up your BaseCamp folder just in case it has problems, and it should recover as much as can be recovered. The most data you could lose would be non-geolocation data for tracks you duplicated in 3.2.1.

The only alternative I can think of is that if you had this data in 3.1, you can instead just rename your ~/Library/Application Support/Garmin/BaseCamp/Database/3.2 folder to something like "My New Data" so BaseCamp can't find it and loads that older data instead. Then you can export your old 3.1tracks to GPX, name your Database/3.2 folder correctly again, and restart and import said GPX file.

Thanks. Yes, I ended up just moving out the 3.2 folder and relaunching Basecamp, so that it would pull the 3.1 data back again. I lost a couple of tracks, but thankfully the majority of it was still there, so I'm back in business!

Crash - possible duplicate

Folks - just downloaded & installed 3.2.2. (iMac 3.06GHz Intel Core 2 duo, running OS X 10.7.1) ... crashes on startup! I looked through the forum & found several solutions proposed, none work.

I don't even have the folders mentioned! How can it be? I have of course uninstalled & reinstalled (all residual files manually removed) - still no success.

Crash report is attached - hope someone can help me out.

Thx a lot in advance.

(PS I have no previous experience with Basecamp, no maps or - obviously - any previous version installed)