|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello, We're having an issue in the latest build (2016.1.39.0) with really large pages that expand as they scroll (Instagram, Tumblr, Facebook). On some of the large pages, we can never finish scrolling to the bottom because the WebView crashes. We are using eowp.exe and have enabled large address space. Here's an example of a page that we can never scroll fully in the control, but can do so in Chrome. http://blackmeansforever.tumblr.com/Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
With the tumbir Url you posted, how far can you scroll down? We tried to scroll down until the page grows more than 100,000 pixel high (which will take a long time) and the render process still only takes about 500M memory. As you keep scrolling, eventually it will always run out of memory, however it will a lot of scrolling to reach that point, which makes it extremely unlikely to be reached by user.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello,
It's hard to gauge how far we get when it crashes, as it's not always in the same place, but I have noticed the worker process get larger than 1GB. I also wanted to note that in Chrome, we can scroll to the end of the tumblr page without issue.
Thanks
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello, I also wanted to add that before getting to this point, the browser is very slow to scroll and load new content. Here's a screenshot of the worker processes and showing there's plenty of CPU/Memory on the box. 
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/26/2015
Posts: 98
|
Hello,
We are still running into this problem with larger sites. It's concerning because the Chrome browser is able to load the page to entirety, although it does get slow once it has loaded a lot of the content.
Thanks,
Peavy
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
We are not sure what can be done on this one. We do have some additional overhead when comparing with Chrome (for example, we have to route many events to the .NET side), so it's not like if Chrome can do a certain number of pages we must be at least the same. Additionally, neither Chrome nor EO.WebBrowser's primary focus is for extremely large pages like this, so it's not a good idea for you to push it to the edge. Due to the enormous size of the browser engine, a systematic optimization is neither practical nor effective.
Thanks!
|
|