Hello community,

I’m currently working with the webbrowser engine and somehow I’m experiencing some webview issues. I have a window that contains a tabconrtol and each tabitem has a webview as child. There is also the main application which has a webview. So at this point when i try to add the fifth tab including the webview to the tabcontrol, the UI of basically all the webviews start to be slower (I have javascript transitions in the webviews). Everything is fine as long as I have 4 webviews. Do you know why this is?

Hi,

thanks for the fast answer. So I just tested the TabbedBrowser and loaded the exact same pages in the same order into the tabs. 3 - 4 Tabs working fine. When I open a new tab you can see that the animations start to lag. I will try to send you a test project.

EDIT: Is it okay, if I just supply the html files as they are enough in order to reproduce it in your TabbedBrowser?

Hi,

We tested your files here and we do not see the problem you described, even if we open more than 10 tabs.

The actual transition is done by the GPU. So you may want to test it on a different system and see if you get different result. You can also run the same test in Google Chrome browser and see if you see the same behavior. We do not have any limits on our side and as far as we know there is no hard limits inside Chromium browser engine either. So most likely the limiting factor is the hardware on your system. Also when you run your test, make sure you have the latest build from our download page.

Thanks!

Hi,

No. There is no difference between the precompiled version and the version you compiled yourself. They are compiled from exactly the same source code. The following area could be the differences:

1. I assume that run the precompiled version without running in under a debugger. If you run your own version under the debugger, then there obviously will be a significant performance difference when it runs under a debugger;
2. When you run the precompiled version directly from the installation folder, it would use eowp.exe instead of rundll32.exe (because eowp.exe already exists in that folder). You can find more information about eowp.exe here:

https://www.essentialobjects.com/doc/common/eowp.aspx

You can achieve the same result with your own version by copying eowp.exe into the same folder as your executable.

Thanks

Hi,

This should have something on your system, not our DLLs. Both version 19 and version 20 are built from Chromium's source code. There shouldn't be such a noticeable performance difference between them. What can make such a huge difference is some kind of application (most likely some security software) on your system that treats them differently. So I would recommend you to check that first.

If you can not find what application on your system that triggered the problem, you can try it on a fresh Windows install with nothing else. That should demonstrate the problem you are seeing. You can then start to put other application on that system and see if you can find out which application is causing the problem for you.

Thanks!

Hi,

I am not sure what else we can tell you. If you can send us the HTML file/link that you are using we can test it here again and see what we can find.

Thanks!

Hi,

We have tested your files where and we do not see any noticeable difference regarding performance between 2019 version, 2020 version and the current version of Google Chrome. Here are our findings:

1. CPU usage increases after every new page. On our test system, it increases around 10% after each page. Google Chrome has similar result;
2. Comparing CPU usage between v2019 and v2020, v2020 is in fact slightly lower (0.5 to 1%);
3. Memory usage are similar between v2019 and v2020. However with v2019 Windows task manager may not count the memory usages of all child process together with TabbedBrowser.exe (with v2020, when you expand TabbedBrowser.exe in task manager, you would see all the child process, with v2019, you may not see any). This would create the misperception of v2019 using less memory than v2020. When in fact they are similar. This might be what you have observed;

Our conclusions are:
1. Your page is indeed CPU intensive. So as you open more pages, it will eventually slow down;
2. We do not believe this has anything to do with the DLL --- it has something on your system that treats v2019 and v2020 differently;

Hope this helps.

Thanks!