Memory Usage

Former Member
Former Member
Just curious about the 'normal' memory usage for Basecamp. I'm just getting started with playing with it and as many (most?) others have noticed the performance is terrible (I experience slow redraw's, stalling, excessive HD access, and overall poor performance so far).

Here is an observation for the dev's and specifics on my machine with some hopes that it will help the community.

Let me first say that I truly appreciate such a nice effort by Garmin to support it's users (via this application) but also that I recognize this free product as an integral part of supporting those users and add on products (such as BE, which I just bought).

Here's my observation:

Just started Basecamp. The application is currently using 285Mb of RAM (and climbing). I had it opened a few minutes ago and it was using a similar amount of RAM. When I tried to close the application it took a full 5 minutes to close the visible window and then the process hung around in the background for about another 5 minutes gradually decreasing the memory in a few hundred KB increments until it finally closed.

What I know (or perhaps recognize): The application is currently connected to my Oregon 400t, and is syncing (caching) the Topo 2008 maps to the desktop (a long process considering the USB v1.1 transfer speeds of the Oregon 400t - another gripe but truly the only one I've had on the Oregon 400). This could explain the large memory usage, however the application gobbled up over 150Mb which I first launched it, then jumped to over 250Mb once it saw the connected Oregon 400t.

What I'm really curious about is what kind of memory should I expect this application to be using? This amount seems terribly high to be rendering a best a few hundred square miles of mapping product (currently showing Topo Kentucky from GPS File Depot).

My rig:
Core2Duo E6400 2.13Ghz, 4.0Gb RAM (3.25 usable in Win7 32bit)
Windows 7 Professional 32bit (fully patched with all current OS updates)
Nvidia GeForce 9800GT Video 512Mb onboard RAM (196.21 drivers)
500Gb Hard Disk Storage (System Partition, 2 x 250Gb drives in RAID 0)
Video running at 1440 x 900

Hope this helps someone :)
  • Former Member
    0 Former Member over 15 years ago
    Interstingly the memory issue could just be related to the syncing of Topo 2008. After a little over an hour the memory usage has grown to over 850Mb :eek: for Basecamp.exe. The sync process is about 3/4 done.

    Hmm.
  • Well on both my Desktop (8GB RAM, Phenom II @ 3.5Ghz, 2500x1600 resolution powered by onboard 790GX), and my 4 year old Laptop (Pentium M 780, 915GM graphics, 2GB RAM, 1280x800), Basecamp 3 runs really quick. Especially in 3D mode (though rendering quality is worse in 3D - like Mapsource 6.14-6.15 quality).

    Basecamp will use up to 1/4 of available memory AFAIK (but max 850MB). It caches maps in advance to memory, so that map panning is quicker.

    Even if showing a very high detail Birdseye Imagery download, it still stays pretty quick.

    I would not mind it using even more (let's say 3-4GB RAM), if it became quicker. I'ld much rather have the possibility inside the program to switch of caching to HDD, instead of chowning the cache folders.

    See also the info here: https://forums.garmin.com/showpost.php?p=33761&postcount=9

    Edit: sorry, no max 850. Correctly used a bit more ~ 1.3GB, though that was less than 1/4 of the available memory (it should have used up to 1.7GB)
  • Former Member
    0 Former Member over 15 years ago
    BaseCamp did run MUCH better when I only had no or juat a few BirdsEye downloads on it. It slows down progressively and crashes more as you compile imagery. I completed 6 or 7 so transfers at the highest quality setting, largest square possible before it became useless. I think the problem lies with BaseCamp trying to load all of this info into RAM.

    At the worst point, I was seeing 700MB of Ram usage before I even get the BaseCamp logo pop-up. Then as it loads up.... lets say 5 minutes later... I am using nearly 2 GB of RAM and then it crashes with absolutely no imput from me.

    I just got an idea and I'll think I'll start a new topic called "How to fix BaseCamp"