2024-04-08, 08:23:47
Hi,
That's weird.
First off, the AntView global object is global to the application and not to the whole of the windows operating system.
The "--app-id" chrome flag that you tested this with is not intended to just randomly add a tag, it was designed for application-mode.
See the following links for a bit of an idea:
https://peter.sh/experiments/chromium-co...-switches/
https://askubuntu.com/questions/1222021/...cli-option
https://superuser.com/questions/33548/st...ation-mode
I'm not too surprised that adding an app-id doesn't work well with WebView2 and I wouldn't draw conclusions from using it.
Just to rule out this path.. some additional questions from my side as I am not that familiar with Progress OpenEdge.
I expect that each time you start a new version of your application that it has its own process ID.
In other words, when you look at your application instances from Windows Task Manager, I would expect to see two lines in the "Details" tab and each having it's own "PID" number.
With that out of the way, let's see if we can figure out what is happening here.
It certainly is not something I would expect to see.
Can you tell us more about the process that is keeping the first instance busy?
What is it processing? Is this waiting for a website to complete.. something else?
What AntView method is being called in the first instance when the process is waiting?
thanks,
--
Wil
That's weird.
First off, the AntView global object is global to the application and not to the whole of the windows operating system.
The "--app-id" chrome flag that you tested this with is not intended to just randomly add a tag, it was designed for application-mode.
See the following links for a bit of an idea:
https://peter.sh/experiments/chromium-co...-switches/
https://askubuntu.com/questions/1222021/...cli-option
https://superuser.com/questions/33548/st...ation-mode
I'm not too surprised that adding an app-id doesn't work well with WebView2 and I wouldn't draw conclusions from using it.
Just to rule out this path.. some additional questions from my side as I am not that familiar with Progress OpenEdge.
I expect that each time you start a new version of your application that it has its own process ID.
In other words, when you look at your application instances from Windows Task Manager, I would expect to see two lines in the "Details" tab and each having it's own "PID" number.
With that out of the way, let's see if we can figure out what is happening here.
It certainly is not something I would expect to see.
Can you tell us more about the process that is keeping the first instance busy?
What is it processing? Is this waiting for a website to complete.. something else?
What AntView method is being called in the first instance when the process is waiting?
thanks,
--
Wil