Recently i've found some abnormal delays on my application and i could not find the cause ; for instance, when i click to close a MDI form, the form will close only about 10 seconds after i click on the close button, instead of closing right after i click like it always was.
So to try to diagnose the problem i started to use Process Monitor (https://learn.microsoft.com/en-us/sysinternals/downloads/procmon) to see what exactly my app's process is doing.
As recommended, on my application i use an external subprocess on GlobalCEFApp.BrowserSubprocessPath, so i'd expected that all things related to CEF4Delphi would be handled by on these sub-process , and in fact, a lot of these subprocesses EXE files are open in task manager.
But when i monitore my app's process using procmon, i see a lot of activity generated by my EXE file that is not related to my application itself, but to CEF. Things like cookies writing, webstorage and access to registry entries that is not being made by my app, but by the navigator.
Is this the expected behaviour or am i missing something ?
Disclosure Statement: This site contains affiliate links, which means that I may receive a commission if you make a purchase using these links. As an eBay Partner, I earn from qualifying purchases.
About subprocesses
- salvadordf
- Posts: 4580
- Joined: Thu Feb 02, 2017 12:24 pm
- Location: Spain
- Contact:
Re: About subprocesses
Hi,
These links show how Chromium loads a web page using multiple processes :
https://www.chromium.org/developers/design-documents/multi-process-resource-loading/
https://www.chromium.org/developers/design-documents/multi-process-architecture/
These links show how Chromium loads a web page using multiple processes :
https://www.chromium.org/developers/design-documents/multi-process-resource-loading/
https://www.chromium.org/developers/design-documents/multi-process-architecture/
Sometimes the Chromium developers decide to create move some functionality to a new process. The information in the previous links may change in the future.All cookies are handled by our CookieMonster object in /net/base. We do not share cookies with other browsers' network stacks (e.g. WinINET or Necko). The cookie monster lives in the browser process which handles all network requests because cookies need to be the same across all tabs.