Access instance remains in memory once closed

[isladogs]

@KitaYama
The tests are to use code to open a new Access instance (or an external database) then close it again in code.

Using Win 10, @CJ_London, myself and @AHeyne all confirm that the separate instance of Access is ALWAYS removed from the Task Manager

Using Win 11 (which I don't have), @CJ_London & @arnelgp both ALWAYS see a hanging instance left behind in task manager background processes. You appeared to be saying that for you there was no instance remaining in task manager using Win 11.

EDIT: After watching your video all the way through, your last reply seems to confirm that the background instance IS deleted

Just noticed @Gasman's reply. Also removed for him using Win 11

 

[KitaYama]

@KitaYama
The tests are to use code to open a new Access instance (or an external database) then close it again in code.

Using Win 10, @CJ_London, myself and @AHeyne all confirm that the separate instance of Access is ALWAYS removed from the Task Manager

Using Win 11 (which I don't have), @CJ_London & @arnelgp both ALWAYS see a hanging instance left behind in task manager background processes. You appeared to be saying that for you there was no instance remaining in task manager using Win 11.

EDIT: After watching your video all the way through, your last reply seems to confirm that the background instance IS deleted

I feel I'm being dumb and don't understand.
This is what my gifs showing:
I have a database opened. So I have one process of Access.
From current opened database, I run a code and open another database. It becomes two processes of Access.
I close the database I opened, it becomes one process.
The process that is left is current database.
Should I close this current database too and check what happens?

thanks

 

[KitaYama]

EDIT: After watching your video all the way through, your last reply seems to confirm that the background instance IS deleted

Oh God....What a relief.
For a moment I thought I've lost my mind and can't understand a simple task.

 

[isladogs]

No - you are describing exactly the same as I said after editing the final sentence!
I had only watched part of it when I first replied. My bad . . .

 

[AHeyne]

Using Win 10, @CJ_London, myself and @AHeyne all confirm that the separate instance of Access is ALWAYS removed from the Task Manager

I don't want to make it unnecessarily complicated, but I haven't even mentioned my operating system yet. However, I use Win 11 23H2, not Win 10.

 

[isladogs]

Sorry I must have just assumed you were on Win10.
Actually I think that may have helped confirm this isn’t a general bug related to Win 11 but may be specific to certain workstations only.

I’ve asked several other colleagues to check in Win 11 as well.

 

[AHeyne]

Maybe the version of Windows 11 makes a difference? I've in my mind that 24H2 is more buggy than others...

 

[Gasman]

Maybe the version of Windows 11 makes a difference? I've in my mind that 24H2 is more buggy than others...

Yet I have no instance left?

 

[AHeyne]

That's a good point.

 

[CJ_London]

I'm on windows 24H2 and updates are apparently up to date

 

[CJ_London]

I’m going to look into this suggestion:

Spoiler

Dear Tech Support,

Last year I upgraded from Boyfriend to Husband and noticed a distinct slowdown in overall system performance, particularly in the flower and jewellery applications, which operated flawlessly under Boyfriend.

In addition, Husband uninstalled many other valuable programmes, such as Romance and Personal Attention and then installed undesirable programs such as Football, Golf, Football, Sailing and Continuous TV. Conversation no longer runs, and Housecleaning simply crashes the system.

I've tried running Nagging to fix these problems, but to no avail. What can I do?

Signed, Desperate.

Dear Desperate,

First keep in mind, Boyfriend is an Entertainment Package, while Husband is an Operating System. Please enter the I Thought You Loved Me app and run the Tears function. You may like to try the Guilt function also.

If that application works as designed, Husband should then automatically run the applications Jewellery and Flowers, but remember - overuse of the above application can cause Husband to default to Grumpy Silence, Garden Shed or Beer. Beer is a very bad program that will download the Snoring Loudly Beta.

Whatever you do, DO NOT install Mother-in-law (it runs a virus in the background that will eventually seize control of all your system resources). Also, do not attempt to reinstall the Boyfriend program. These are unsupported applications and will crash Husband.

In summary, Husband is a great system, but it does have limited memory and cannot learn new applications quickly. It also tends to work better running one task at a time. You might consider buying additional software to improve memory and performance.

Good Luck, Tech Support.

 

[isladogs]

@CJ_London
Just to confirm that I've had a response from a fellow MVP (Karl) who tested in a Hyper-V VM with W11, A365, 64 bit, latest CC build.

The instance (with or without a db) appears as background task with the New line and goes away with the Quit, as it should do.

This provides further confirmation of my belief that that there isn't a general issue affecting Win 11 users.

 

[CJ_London]

hmm - still doesn't for me on win 11

 

[isladogs]

Unfortunately some issues appear to affect a limited number of machines. I have two different long standing bugs that others can’t replicate.

I’ll watch out for other reports in case it is a broader issue than it currently appears to be

 

[Minty]

Just to confuse or conflate matters, I had this happen to me ages ago, on Windows 10 - A rogue Access process left behind, after closing a database either manually or in code.

I never got to the bottom of it (tried office repair, remove and reinstall etc. etc. ). I only made it go away when I moved to a fresh install of Win 11.
Something somewhere in the inner machinations of Windows or Office was borked.

 

[RonPaii]

I have 1 user with Grammarly installed having this issue, Windows 10 x64. There was a patch that mostly fixed it.

From AI
Having Grammarly installed can cause Microsoft Access to stay running in the background after it's been closed, leading to a "zombie" process in memory.

 

[dalski]

I've experienced this MANY times & it has always been as per @RonPaii's suggestion - a circular reference caused by my bad code not terminating a circular reference. When studying basic C# & C++ (very basic courses) I & the article refer to them as memory leaks. But I've been informed by someone much more capable than me that that's not entirely correct & I'd take their word over mine every day of the week. Also pretty much everyone in this thread is more experienced than myself.

 

[CJ_London]

The problem with that is there is no circular reference as far as I can see - open an access instance, then close it. I’m not even assigning a .accdb