Does anyone have any ideas as of yet ?

For what it is worth, I tried Chrome Stable and Canary on Win 10 Professional 32 bit and there are no issues.
I don't have 64 bit.

Anything this fatal would have to be something specific to the machines. without having access to the exact configuration and being able to reproduce, it will be hard to make any progress on this bug.

The bug report claims no extensions present but there are a few lines in the attached logs (I analyzed the AMD log) that hint at extensions trying to start:

[8588:7560:0425/121721:INFO:CONSOLE(9)] "KasperskyNativeMessagingClient OnDisconnect", source: chrome-extension://dbhjdbfgekjfcfkkfjjmlmojhbllhbho/background/main.js (9)
[8588:7560:0425/121721:INFO:CONSOLE(239)] "NM exception: Error: Attempting to use a disconnected port object
stack:Error: Attempting to use a disconnected port object
    at Error (native)
    at PortImpl.postMessage (extensions::messaging:65:22)
    at Port.publicClass.(anonymous function) [as postMessage] (extensions::utils:94:26)
    at KasperskyNativeMessagingClient.call (chrome-extension://dbhjdbfgekjfcfkkfjjmlmojhbllhbho/background/common/native_messaging_client.js:140:24)
    at StartInitializeExtension (chrome-extension://dbhjdbfgekjfcfkkfjjmlmojhbllhbho/background/main.js:35:9)
    at Object.callbackError (chrome-extension://dbhjdbfgekjfcfkkfjjmlmojhbllhbho/background/main.js:30:2)
    at KasperskyNativeMessagingClient.callbackAllPendingOperations (chrome-extension://dbhjdbfgekjfcfkkfjjmlmojhbllhbho/background/common/native_messaging_client.js:246:36)
    at chrome-extension://dbhjdbfgekjfcfkkfjjmlmojhbllhbho/background/common/native_messaging_client.js:93:22
    at EventImpl.dispatchToListener (extensions::event_bindings:387:22)
    at Event.publicClass.(anonymous function) [as dispatchToListener] (extensions::utils:94:26)", source: chrome-extension://dbhjdbfgekjfcfkkfjjmlmojhbllhbho/background/common/native_messaging_client.js (239)

and some more which I didn't bother to check yet if they are packaged with Chrome or further standalones.

It seems the machine is part of Active Directory domain. Can you also add the contents of the chrome://policy page and maybe a screenshot of the chrome://extensions page. Another thing I notice is this line:

[8588:5192:0425/121721:VERBOSE1:proxy_service.cc(1229)] Failed configuring with PAC script, falling-back to manual proxy servers.

Not sure if this is always shown when there is no PAC script or of you are actually trying to use pac script which fails to work as expected. All those can delay the network initialization indefinitely long.

Hi,

I just added the output of chrome://policy and chrome://extensions as requested.

Both files are in the same shared folder restricted to Google at https://drive.google.com/a/google.com/folderview?id=0Bxg-rTzA58Ped1RicFJpZnNKaFE&usp=sharing

Thanks

Now it is obvious that there are plenty of extensions and specifically the Kasperski extension which will be checking every URL loaded (waiting for the connection to the AV through the native messaging host to be established. Can you please try to disable the Kasperski extension and verify if the issue persists?

Gentle Ping! There is no update on this issue since long time, could any one let us know what's the current status of the issue?

Thanks!

There has beem no answer on my last question on this thread, namely:

Can you please try to disable the Kasperski extension and verify if the issue persists?

Hi, yes, the antivirus was disabled, and still, the issue persisted.

Can you please provide the log files of the session where the Kasperski extension has been disabled?

Closing this. Feel free to reopen if it's stil happening.