MS Access Memory Issue

Question

Programming in Access 365 but it is a 32-bit access front end with a SQL Express backend. Been using this database for years with no issues. All of a sudden starting approx. last Monday 12/12/2022 we started getting out of memory errors on the client side. Users started getting it randomly over 2 or 3 days as if it was an update.

If I open the database and watch task manager, as I open forms and close them, I see the memory usage go up when the form is opened as expected but it never goes back down to where it started from when the form is closed. We have a few form timers that run code every 2 to 5 minutes and the same thing happens, memory usage goes up when the timer triggers but when the code finishes the memory is not released.

I have run CHECKDB on the SQL Express tables, I have also run a SQL Shrink Database. On the front end, I have decompiled the database, run a compact and repair and then recompiled it.

I have been able to reproduce the issue on a computer at my house with a different access database. This database is a 64-bit database with access tables not SQL. The same thing happens, when I open forms then close them the memory usage does not return to the amount before the form was open, always just a little higher until I get the error message.

Answer 1

@Karl - Yes, on your advice, I rolled back to Version 2210 (Build 15726.20202). I repeated the same test and found that the problem was resolved. In fact, running these make table queries does not cause Access.exe to consume any additional memory.

I then rolled forward to Version 2211 (Build 15831.20190). I repeated the same test and found that the problem returned.

This seems to confirm that the problem emerged in version 2211.

Answer 2

Hi,

I think the version dependency and RAM emergency is becoming always clearer. What remains is the difficult reproducibility for others (including Microsoft), as so often when SQL Server is involved.

I will try to find the best way for a reproduction scenario with someone in charge at Microsoft, and/or get someone directly involved here (and in the parallel discussion here).

Servus

Karl

Answer 3

Much appreciated Karl! This thing has been a support nightmare for us. Some IT guys don't want to turn off updates or adjust.

Please keep us posted or ask if you need input or help.

Scott

Answer 4

Hi,

We still lack a reproduction scenario to achieve anything at Microsoft.

If someone can reliably generate the problem on their end, perhaps they could do the following:

1. create a copy of the SQL Server db
2. reduce the copy to the necessary tables/views to get the error
3. anonymize data, if necessary
4. script out the resulting db
5. reduce the frontend to the necessary parts to get the error
6. make a zip file with the resulting frontend+backend available and inform us

I know this is a bit elaborate, but it's currently my only idea to get something going.

George has also updated his doc article to say that we primarily need a repro scenario.

Servus

Karl

Answer 5

@Karl - As you noted, it will take a substantial amount of work to put that sample data/scenario together. I can do so, but will wait to do so until I get some additional feedback directly from Microsoft (on the ticket I already have open). This week they collected a screen recording and some other details regarding the issue, so I'm hoping a request for more technical details will follow.

I'll share any relevant updates here.