Hi!

I updated my EO.WebBrowser for WindowsForms 18.3.46.0 version to 20.1.45.0 and I noted a increasing of memory consuption.

The previous version used to run only one Windows Host Process(Rundll32) attached to my process around 80 MB of memory. And now, the current version runs 5 Windows Host Process(Rundll32) attached adding up 400 MB memory.

It initiliazes the runtime with these arguments:



Considering we have a 2 years gap between the updates so I ask:
Is it right? Is there anything I can do to improve this?


Thanks

Hi!

So chrome's reputation about the memory is bullshit? Just kidding =)

Let me see if I got it right

When do you talk about read only memory sections, you mean private memory, shared memory and working set or you mean only private memory?

In the linked post, there is the 70M (50M + 20M) example. In this case, which one is this?

1) 70M (working set) = 50M (private memory) + 20M (shared memory)

or

2) working set = 70M (private memory) + shared memory

I gathered some info from Process Explorer by SysInternals that shows all these memory information separately

18.3.46.0

process | ws private| ws shareable| ws shared| working set|
rundll32 | 1168 K | 81508 K | 81508 K | 82700 K |
rundll32 | 74516 K | 31604 K | 31604 K | 106144 K |
rundll32 | 87360 K | 23872 K | 23872 K | 111256 K |

20.1.45.0

process | ws private| ws shareable| ws shared| working set|
rundll32 | 1572 K | 115742 K | 115742 K | 117068 K |
rundll32 | 102916 K | 34560 K | 34560 K | 137500 K |
rundll32 | 100756 K | 23252 K | 23252 K | 124032 K |
rundll32 | 112684 K | 30052 K | 30052 K | 142760 K |

I found a post at https://www.chromium.org/developers/memory-usage-backgrounder, talking about a misunderstanding in memory measure on Windows XP, because its Task Manager shows the working set instead of private memory

Thanks !