OpenStreetMaps causing frequent crashes

It looks like we have regressed our handling of corrupted OpenStreetMaps in BC 4.5.0. Until the fix comes out, you will need to remove the corrupted map.

If you are consistently crashing, especially on startup, then it's likely you're using a corrupted OSM. You can either remove your maps one and a time (starting with OSM) until BaseCamp starts w/o crashing or look in the crash log. If you search on 'Activity:' in the crash log, then you'll find the failing map on the next line.

You can use MapManager to add and remove maps or if you are so inclined you can attempt the following steps:

To remove a map from a device:
1. Stop BaseCamp
2. Open Finder and look in your Garmin folder on the device.
3. The .img files are your maps. You can delete those, or just rename them using a different extension like .img.bad.
4. Start BaseCamp

To remove a map from BaseCamp:
1. Stop BaseCamp
2. Open Finder and select 'Go->Go To Folder'
3. Enter ~/Library/Application Support/Garmin/Maps
4. Delete the map you don't want or move it to another folder
5. Start BaseCamp again

Once you get BaseCamp up and running again, you can probably re-download your OSM and it will work just fine.
  • To remove a map from BaseCamp:
    ....

    Why not using Garmin MapManager for that?
  • Former Member
    0 Former Member over 9 years ago
    Proposed fix does not seem to have any effect

    It looks like we have regressed our handling of corrupted OpenStreetMaps in BC 4.5.0. Until the fix comes out, you will need to remove the corrupted map...<snip>...Once you get BaseCamp up and running again, you can probably re-download your OSM and it will work just fine.


    I use OSM maps with a Zumo 660, and I also am experiencing crashes with BaseCamp 4.5.0. I'm not sure what type of "corrupted" maps the previous post is referring to, but I tried the advice above and removed all third-party maps from my device (.img files that I had installed into the Garmin directory). I also had a single OSM map that had been installed to BaseCamp which I removed. Once BaseCamp and the Zumo were running correctly with no OSM maps or other third-party maps, I downloaded a new supplemental OSM map (again, as an .img file), and installed that to the device. Immediately BaseCamp started crashing again, with the same error as before.

    It seems quite likely to me that the new version of BaseCamp was not tested at all with OSM .img files. I have reverted to BaseCamp 4.4.8 and will be much more careful about updating the software in the future, although I do hope the problems with 4.5.0 are addressed soon. Of course, Garmin is not obligated to support third-party maps, but for me and many other people, failing to support third-party maps would make these devices far less useful. (In particular, I use English-language topo maps of Japan on my Zumo 660...Garmin doesn't have any English-language maps of Japan at all, and I don't think there are any topo maps of Japan available with the Zumo 600, even in Japanese).
  • Former Member
    0 Former Member over 9 years ago
    It looks like we have regressed our handling of corrupted OpenStreetMaps in BC 4.5.0. Until the fix comes out, you will need to remove the corrupted map.


    Please elaborate on how the OSM map files are corrupt. I am experiencing the same situation as the previous poster in that all sources of OpenStreetMaps maps I have tried cause BaseCamp 4.5.0 to crash. If there is a genuine problem with the OSM files for Garmin devices maybe OSM and other 3rd parties that generate images from OSM data need to be notified of the issue in order that they may generate non corrupt files.
  • It's not the maps as I have loads of OSM maps running on my Basecamp 4.5 but in Windows.
  • OSM maps have always been extremely variable in their level of "correctness", which is one reason Garmin can only officially support the ones it releases with biking products, though there is no attempt to not support them. We did find the issue with OSM maps in the Windows version before we shipped, but unfortunately the fix wasn't rolled into the Mac version. There will be a new version out (hopefully next week) that fixes the crash. At the same time, in our testing on the Mac, we actually had trouble reproducing the issue, because one day's version of the map was wrong and the next day's could be right. In the meantime, your options are to remove all OSM maps until 4.5.1, or you can follow Wurth's instructions for isolating the maps that are causing the issue.*
  • Why not using Garmin MapManager for that?


    Good point. You can use MapManager to delete it or to show the map in Finder if you want to move it.
  • Why not using Garmin MapManager for that?


    Because that would be too easy! Thanks for pointing that out. I'll update my post
  • Former Member
    0 Former Member over 9 years ago
    Thanks for fixing this, 4.5.1 seems to work fine with OSM.