Thanks for the update. I’ve been doing a lot of profiling and testing this weekend. I’ve found a few places I can improve, and I’m now seeing typical memory usage around 60-70MB (as shown in Task Manager).
Interestingly, if I remove the the embedded browser component, memory usage drops to about 40MB, so that’s taking about 20-30MB of in-process memory, plus whatever’s used by CefSharp.BrowserSubprocess.exe.
I’ve added memory usage logging, which will be in the next release. If we can’t get to the bottom of this before then, maybe that will give us some more clues.
That’s definitely not right - I’ve never seen it take so long myself, so there’s something happening in your setup which isn’t present in mind, I presume. Does it respond quickly when it’s first been started?