This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Asking again since they refused to answer last time

https://forums.garmin.com/apps-software/mac-windows-software/f/garmin-express-windows/305155/is-there-a-known-issue-with-garmin-express-requestcache-db-being-over-600gb/1497064

I never got an answer for the question I asked (this could be a zero day in Garmin's software and Microsoft might ban the program due to the nasty bug).  Does Garmin not care at all that their software issues filling up storage devices with unknown data in a .db file?

Not interested in a bs no effort answer like I got last time that failed to answer the question.  I ask what the .db is and never got an answer.

This is technically a security bug in Garmin Express if it fills up people storage devices with unknown content in 1 .db file (the file is over 600GB and growing), yet a refusal to answer a simple question is weird.

  • As I said before you don't have to have any Garmin device connected for it to grow that big.

  • ...and as I said before, and a few others also, you seem to be the only person who has experienced the issue.  You have also been told that the request.db file can be deleted, and the device will recreate a properly sized file of the same name.  If THAT recreated file then grows, then a problem may exist, but until you delete the problematic file, I doubt you will get input from the members of this forum.

  • No can't be just me, and as I said I am posting for a friend trying to figure out what the .db is for.  Why would it grow to that massive of a size (it is about .5TB) if the Garmin device is only connect to the computer for a few minutes a week.  It was never answer what the .db is for (hard to know what to look into if I don't know what creates that database for and what it is used for aka hard to troubleshoot if just getting a refusal to answer a simple basic question.

    The fact that it is about 200 to 600% or more the size of many peoples C: drive is not weird?

    I am not sure if you could even send the file to support as it is over 600GB uncompressed and under 20 KB compressed (which takes over 26 hours to compress that causes Windows to hang during the compression).

  • OK, so it isn't you, it is your friend.   But as I said in the prior thread, if I just do a search on the file name you've referenced Google has 29,900 hits, and your input seems to be the only input relative to Garmin.  If I add "Garmin" to the search, I get 2500 hits, again very few applicable to your problem.  You have also been told by Garmin support to delete the file so JUST DO IT!  Quit suffering from analysis paralysis.

  • The Garmin Express app is nearly bricking Windows PCs is not weird (when the file is on the machine at that size you can't use the machine as it might take 7 minutes to open Windows explorer as index is stuck trying to index it and anti malware programs have trouble with the massive file)?   Others might now have noticed the bug, it is over a year old (the size grows slowly tho I don't know what causes it to grow).
    I never got an answer to as what the .db file is being used for (they are not using any GPS maps, and no clue why info from a Garmin Watch would use over .5TB of storage).

    I already did a search and there was nothing related to the issue I am seeing, that is why I asked in the forums here to see if others had seen it and what the strange .db file is (still no answer as to what it Is for) doing that it is so massive which is about 419444 floppy disks.  I would guess Garmin support machines don't have 1TB drives in each computer where they could uncompress the file if they got it (tho it might take them 2 or more days to uncompress it).

  • What the heck is the aversion to deleting the file?  And to do so I would highlight the file, then do a shift-delete which will remove ot without stuffing it into the Recycle Bin.

  • It will be the same in a short period and does not fix the issue (also don't know what the .db is used for).

  • As this is going in circles I'm closing comments. Take the advice given numerous times and delete the file. If you're concerned copy it somewhere else.