WIX NOT ENOUGH MEMORY TO OPEN THIS PAGE PLUS
In Markdown Monster I've been using the WebBrowser control for a heavy interfacing with ACE Editor as an editor control plus a preview and one thing that really stood out is that overall memory usage of the application was pretty low (around 100-150mb typically even with a number of editors open). Happy to be corrected about that Totally agree on the WebBrowser versus WebView debate. To my best understanding, it's expected to still be around at least until 2019. The problem is, Microsoft is somewhat unclear about when (if ever) IE11 is going to be removed from Windows.
WIX NOT ENOUGH MEMORY TO OPEN THIS PAGE WINDOWS
it still receives security updates as part of Windows updates.nothing needs to be installed or bundled.
its feature set is frozen which means more stability, predictability and fewer bugs.
Trident is still a decent HTML5 renderer.IMO, Embedding WebBrowser (or MSHTML part of it) is still a viable tool and has many advantages: When looking at other web controls (like WebBrowser) we believe we are competing on other aspects as well
I picked Electron for my own SaaS project over Chromely only because I feel Chromely doesn't have enough backing from some big players yet. I believe Chromely is very important because currently it's is the only framework to build self-contained, cross-platform desktop HTML apps with C# and. However, that doesn't mean that WebView2 will always be the right choice, and I think your example of just needing a textarea in an app is a great example where maybe WebView2 isn't the best option, especially if there are any constraints around memory (low-spec hardware, etc.)Ĭhromely is new to us, so thanks for sharing! When looking at other web controls (like WebBrowser) we believe we are competing on other aspects as well, like having access to a modern and secure web platform. On the WebView2 side there's probably limits to what we can/will do, as it is mostly work done by other teams on Edge. If it's still using CEF/Chromium under-the-hood I would expect it to be similar to the other chromium-based controls, so my first inclination would be to check if it's something to do with the process/memory reporting (like maybe it has a process that doesn't show up directly in the tree, but parented somewhere else, etc.)įor Edge as a whole we care a lot about the fundamentals, of which memory footprint is a piece. Also should control for the size of the web controls, though on static pages I don't think that should have too much of an effect.Ĭhromely is new to us, so thanks for sharing! Curious that using CefGlue saves a few hundred megs. I agree that something like would be better, or even your own test page that you make, to keep the different tests as close as possible. (WS Private Bytes + WS Shared Bytes = Working Set Size). In ProcExp, the setting the matches the data TaskMgr gives is the "WS Private Bytes" column.
0 kommentar(er)
