Windows app instance is still running even after we close the application

Question

Windows app instance is still running even after we close the application

Sunil A M 171

Hi Team,

we have implemented single instancing of winui3 application using the below link,

https://gist.github.com/wbokkers/af326da5391bdb13b58529e720540178

after consuming above implementation in my winui3 application, When i try to close the application by clicking on the close Icon(X mark), Application is getting closed but Still instance of the application persist in the task manager.

Steps to reproduce:

Launch the winui3 app
Close the Winui3 app by clicking on close(X} button.
APplication closed but instance of the app still persist in the task manager.
so that when i try to open another instance of the application because we have implemented single instancing.

Could you please help me to resolve this issue.

Best Regards,

Sunil

Jeanine Zhang-MSFT 11,356 Reputation points Microsoft External Staff

2023-10-13T08:15:53.87+00:00

I test the offical single-instanced sample, and I couldn't reproduce the issue.

According to the Doc:Single-instanced apps

If you want your Windows App SDK (WinUI 3) app to be single-instanced like your UWP app is, then you can override the default behavior described above. You'll use AppInstance.FindOrRegisterForKey and AppInstance.IsCurrent to determine whether the current instance is the main instance. If it isn't, then you'll call AppInstance.RedirectActivationToAsync to redirect activation to the already-running main instance, and then exit from the current instance (without creating nor activating its main window).

Could you please tell us which version of the Windows App SDK you are using? I suggest you could try to use Windows App SDK1.4.
Sunil A M 171 Reputation points

2023-10-13T09:19:57.8833333+00:00

Thanks for the reply.

I am using the below version of the windows app sdk currently in my solution.'

You said, we can override the default behavior described above(in your reply)- COuld you please provide the link( i did nnot understand what is the context)

Note: This issue is happening very rarely in our app - Frequency rate(2/10)

Best Regards,
Sunil
Jeanine Zhang-MSFT 11,356 Reputation points Microsoft External Staff

2023-10-17T07:46:02.4566667+00:00

I'm so sorry. I provided the wrong link. And I've modified the link, please check it again.

For detailed steps on how to implement a single-instanced app, you could refer to the blog: https://blogs.windows.com/windowsdeveloper/2022/01/28/making-the-app-single-instanced-part-3/

Here is a sample about the single-instanced app: https://github.com/jingwei-a-zhang/WinAppSDK-DrumPad, you could test it and to check if the same issue occurs.

Your answer

Jeanine Zhang-MSFT 11,356 Reputation points Microsoft External Staff

2023-10-13T08:15:53.87+00:00

I test the offical single-instanced sample, and I couldn't reproduce the issue.

According to the Doc:Single-instanced apps

If you want your Windows App SDK (WinUI 3) app to be single-instanced like your UWP app is, then you can override the default behavior described above. You'll use AppInstance.FindOrRegisterForKey and AppInstance.IsCurrent to determine whether the current instance is the main instance. If it isn't, then you'll call AppInstance.RedirectActivationToAsync to redirect activation to the already-running main instance, and then exit from the current instance (without creating nor activating its main window).

Could you please tell us which version of the Windows App SDK you are using? I suggest you could try to use Windows App SDK1.4.
Sunil A M 171 Reputation points

2023-10-13T09:19:57.8833333+00:00

Thanks for the reply.

I am using the below version of the windows app sdk currently in my solution.'

You said, we can override the default behavior described above(in your reply)- COuld you please provide the link( i did nnot understand what is the context)

Note: This issue is happening very rarely in our app - Frequency rate(2/10)

Best Regards,
Sunil
Jeanine Zhang-MSFT 11,356 Reputation points Microsoft External Staff

2023-10-17T07:46:02.4566667+00:00

I'm so sorry. I provided the wrong link. And I've modified the link, please check it again.

For detailed steps on how to implement a single-instanced app, you could refer to the blog: https://blogs.windows.com/windowsdeveloper/2022/01/28/making-the-app-single-instanced-part-3/

Here is a sample about the single-instanced app: https://github.com/jingwei-a-zhang/WinAppSDK-DrumPad, you could test it and to check if the same issue occurs.

Share via

Windows app instance is still running even after we close the application

Your answer