|
|
Rank: Advanced Member
Groups: Member
Joined: 11/3/2015
Posts: 65
|
Hello,
I noticed that the browser is slowing down during the day.
So if I open my program using eo webbrowser at morning it runs programs as fast as the Chrome browser. But in the evening it's much slower.
Than I tried to use the tabbed browser. Same Problem.
Than I tried to use the tabbed browser newest version. Same Problem.
Even if I start the tabbed browser at the morning, leave it alown and use it in the evening it's slow.
Do you know, how I can solve this problem (Without restarting the program ... )?
Best regards.
Marius Kramer
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,083
|
Hi,
There is no way we can tell you exactly what caused this ---- what we do know is that we do not have any logic that would render different performance based on whether it's in the morning or in the afternoon. So it has to be something in your environment. I would try to check the system to see if it has any background task running in the evening, or has anything occupying the network/web server and slows that part down during that time frame.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/3/2015
Posts: 65
|
Well, I think, it's not caused by datetime but by runtime ... if the tabbed browser is running for 8 hours It's much slower, even if I don't use it.
Sorry, if that was not clear.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,083
|
We have not received any report from any other users about such problems. You can try to use our TabbedBrowser to load a well known page (such as Google's home page) and let it run for a while to see if you can duplicate the problem. The problem can have to do with the page or the browser engine itself ---- once you verify that it occurs with simple page we will run the same test here and see what we can find.
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/3/2015
Posts: 65
|
I use it to work with "Profound" that displays a javascript program.
If I Use the normal chrome browser there is no problem, but in tabbed browser it is.
Simple sites are to fast to see the problem, I think.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,083
|
If the issue is related to the page, then there isn't much we can do at this point. There are a number of differences between EO.WebBrowser and the regular Google Chrome browser. The first difference is EO.WebBrowser uses a slightly older version of Chromium. The current version is based on V54, where as the current version of Google Chrome browser is V60. The second difference is EO.WebBrowser always run the browser engine in 32 bit mode (in order to be compatible with 32 bit systems), where as Google Chrome is usually 64 bit on 64 bit system. Both can contribute the issue. We will be resyncing to Chromium very soon and update our Chromium version to a most recent version. So that should help if the issue is related to browser engine optimization. The second one will not change in the near future ---- if that's the problem and you run the same page a 32 bit Google Chrome you would see the same problem. In both cases, it is not practical for us to optimize the browser engine. Chromium is an extremely large and constant moving project that is beyond anyone else beside the Chromium team. So I would definitely looking for alternative options, such as trying to fiugre out what's in your page that's triggering the problem, or simply restart the application to provide relief to the problem. Hopefully when we switch to newer version of Chromium it will improve as well.
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/3/2015
Posts: 65
|
thanks
|
|