Would probably still not be that useful. There isn't much memory and the player mlocks most of it for it's own use. Any codepath that hasn't been executed in a while has a high probability that it was paged out, so it is equally likely that something as simple as a function call is blocking on the disk spinup.

It is fairly easyl to observe, simply run ps auxwww and notice that the RSS size of pretty much every process (except for the player) is significantly smaller than the VM size. When gpsapp is blocked in the hijack waitmenu ioctl, it is completely paged out after a while.

I view this as a good reason to avoid useless and duplicated code. Most problems are avoided when the binary and memory usage are as small as possible. There are limits, with a full streel level database we simply can't avoid disk accesses.
_________________________
40GB - serial #40104051 gpsapp