Unexpected delay between OnLoadingStateChange and OnLoadStar

[callum]

I am trying to diagnose why, when navigating to some URLs in my app, there a long delay (~5 seconds) between my CefLoadHandler::OnLoadingStateChange(...) and CefLoadHandler::OnLoadStart(..) methods being called.

Best guess so far is that I'm not calling CefDoMessageLoopWork() often enough - certainly a possibility however, when the page loads, it functions as expected.

I am using the latest 64 bit CEF on Windows.

Anyone else encounter this and suggest what might be going on ?

[Czarek]

What CEF version? Which method gets called first? Is the page loading 5 seconds?

[callum]

> latest 64 bit CEF on Windows

cef_binary_3.3239.1723.g071d1c1_windows64

CefLoadHandler::OnLoadingStateChange(..) gets called first.

~5 seconds elapse

CefLoadHandler::OnLoadStart(...) gets called

PAge loads instantly in Chrome built from same version of Chromuim

[HarmlessDave]

Does it only happen on the very first page when your CEF app first starts up? CEF does a bunch of one-time initialization at startup that can take from 1-2 up to 10+ seconds on a slow PC. Chrome seems to cheat by doing some of that before they display a window.

[callum]

The "App" is starting up although it's not really an app but rather a DLL that is loaded for each app feature that needs an embedded browser.

Replacing the startup URL with something else like Google home page still takes about the same amount of time.

I'll try to break it out into it's own CEF app and see if it repros - will be easier to share/diagnose like that.

[magreenblatt]

Does the problem reproduce in the cefclient sample application? It could be a proxy resolution delay as described at https://bitbucket.org/chromiumembedded/ ... resolution

[callum]

No, the same page seems to load quickly in cefclient. I'm not using any proxies - or does that resolution step happen in any case?

[magreenblatt]

No, the same page seems to load quickly in cefclient. I'm not using any proxies - or does that resolution step happen in any case?

You can try passing `--no-proxy-server` command-line flag just to make sure that's not the issue.

[callum]

Yep, made no difference.