You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was doing some rapid iteration on an apl and I went off to do some other work and when I looked at the process list later there were 40~ QtWebEngineProcess.exe still running even tho I had closed all the result screens.
The text was updated successfully, but these errors were encountered:
I came here to report the same issue.
I generally leave the app open as to keep my reports easily accessible (thus its open between Windows sleeps) and I just noticed the combined weight of my QtWebEngineProcess processes taking 8% of my processor usage whilst doing nothing.
In addition to QtWebEngineProcess not closing when the related results pages are closed, they seem to be doing something after being left alone for an elongated period of time, or perhaps when resuming from sleep.
Unfortunately this is kind of a "feature", every tab is saved in history until simc itself is closed. I looked into ways of modifying it, but I think it'll take a bit of effort. Judging by the code, it looks like the guy who originally did this was trying to not save result pages in history, but it's certainly still doing it.
However, you can get around this by hovering over the "Close all tabs" button while looking at a results tab, and clicking "Clear all history". This will close all the extra qtwebengineprocess.
I'm not following where the "Clear all history" option is - I can see a "Close All" button when rightclicking a tab in results, but nothing when I hover over it.
Not sure what the advantage is of keeping a tab history since I don't know of any way to re-open a closed tab.
It's kind of hidden, but like I said, I don't think it was intentional that we kept closed result pages, but due to how the thing is coded it's actually pretty difficult to rip out without affecting other things. I'll look into doing it, but it's not high priority at the moment.
I was doing some rapid iteration on an apl and I went off to do some other work and when I looked at the process list later there were 40~ QtWebEngineProcess.exe still running even tho I had closed all the result screens.
The text was updated successfully, but these errors were encountered: