webview slowing down the GUI

steve64 · 2025-04-08T18:16:44+00:00

I'm facing a use case where using a webview inside my app slows down the refresh of other widgets. If I set web.visible to false, then the refresh come back...

Samir

By the way, you didn't tell me if you hide/show the Webview2 manually ?

steve64

I do not have Webview:hostfromfolder() in my app.
I tried various options for hiding/showing the webview widget.

Samir

I have found a bug in Webview.visible property and show/hide methods, but i don't think it's related to the slowdown you have

steve64

ok, let see it when fixed, even if I agree it could not be the main root cause

steve64

I found that MS WebView2 has a 'disable-gpu' flag that could be tried to fix the slowdown due to GPU Process.
Could you please try to investigate this and in case offers the flag at LuaRT API level?

Samir

You can use those flags direclty in the Webview contructor, by providing an "option" field in the table. See [Login to see the link]

steve64

I just discovered this new feature now! Thanks, but I tried the following without any benefit:

ui.Webview(tab.item, {
url = "[Login to see the link].."*",
options = '--disable-gpu --disable-software-rasterizer'
})

Anything wrong on my side? Any other recommended flag?
The WebView2 GPU Process is still there and consuming 30% CPU...
I would like to disable the GPU process completely...

Samir

I cannot help that much on this sorry..did you try to update /downgrade you video card drivers ?

Samir

This should help you [Login to see the link]

steve64

I can't change the video drivers since it is a company managed laptop. Anyway, this is a typical scenario for my target applications. I may not ask other users to update drivers as well.
The strange thing is that the --disable-gpu flag would be expected to work but it does nothing.

steve64

From early tests, using LuaRT 2.0.1 the Webview scenario seems a bit changed (positively).
Now I do not see anymore "GPU Process" a very high usage (around 30%) in the Task Manager, even without any special flag.
The peak can now reaches 20% but in average is a bit less.
Did you optimize something in the new Webview integration?

Samir

Very strange...
No the Webview implementation didn't change at all (only for the new Webview:onThemeChange() event).

steve64

ok, as mentioned it could be sensitive to the context of the application in which is integrated and this changed since last test; with 2.0.1 I'm trying to use the Webview, before was not feasible in all cases

« Previous Page