2.0.8 eating cpu-time

Former Member over 15 years ago

Hi,

I've just tried BaseCamp 2.0.8 briefly. I noticed that it uses all available cpu-time, especially while a routable map-product is selected. For instance City Navigator Europe NT 2010.1.

When selecting Trip and Waypoint Manager v2 maps (came with my first gps), it doesn't use any cpu-time, when idle.

I also suspect some memory-leaking, but hasn't looked any further into that.

Ys
Thomas

XP home SP3 (danish version)

0 Former Member over 15 years ago

Thomas,

Thanks for your comments on BaseCamp.

There is one idea that comes to my mind. When BaseCamp sees a new product for the first time it goes through a process collecting data about the maps and caching it for fast access later on. This should happen only once at startup or after switching to a new map. The process can be rather lengthy, especially with routeable maps as you mentioned.

If the CPU usage doesn't settle down after this caching period there may be something else going on. We are continuously looking for opportunities to improve performance of the application so any additional details on when you see the high CPU usage would be helpful (only when panning the map, with 3d view up, while routing, etc).

Thanks,
Zach