Chrome is unresponsive without --no-sandbox flag!

[Nathan L.]

I just started running into this issue. When I launch Chrome without the –no-sandbox flag it does not load anything. It just sits there in “Loading…” state with a blank page. It does not even load “chrome://settings”!

 

I’ve rebooted my machine, uninstalled Chrome & reinstalled it version “38.0.2125.104 m”. Anybody has any clues as to what may be wrong?

 

Here’s the log from “chrome_debug.log” I’ve captured:

[8888:1492:1014/133909:VERBOSE1:policy_loader_win.cc(434)] Reading policy from the registry is enabled.
[8888:8804:1014/133909:VERBOSE1:multi_log_ct_verifier.cc(76)] Adding CT log: Google 'Pilot' log
[8888:8804:1014/133909:VERBOSE1:multi_log_ct_verifier.cc(76)] Adding CT log: Google 'Aviator' log
[8888:1492:1014/133909:VERBOSE1:pref_proxy_config_tracker_impl.cc(148)] 02A64960: set chrome proxy config service to 02A64A50
[8888:1492:1014/133909:VERBOSE1:pref_proxy_config_tracker_impl.cc(277)] 02A64960: Done pushing proxy to UpdateProxyConfig
[8888:1492:1014/133909:VERBOSE1:install_util.cc(234)] Existing Google Chrome version found 38.0.2125.104
[8888:1492:1014/133909:VERBOSE1:app_list_syncable_service_factory.cc(55)] AppListSyncableServiceFactory()
[8888:1492:1014/133909:VERBOSE1:bluetooth_low_energy_event_router.cc(163)] Initializing BluetoothLowEnergyEventRouter.
[8888:1492:1014/133909:VERBOSE1:app_list_syncable_service_factory.cc(45)] BuildInstanceFor: Default (0593E5A0)
[8888:1492:1014/133909:VERBOSE1:pref_proxy_config_tracker_impl.cc(148)] 02A64000: set chrome proxy config service to 06BD55A0
[8888:1492:1014/133909:VERBOSE1:pref_proxy_config_tracker_impl.cc(277)] 02A64000: Done pushing proxy to UpdateProxyConfig
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension Bookmark Manager
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension Cloud Print
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension Web Store
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension Chrome
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension Google+ Hangouts
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension hotword helper
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension Settings
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension Feedback
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension Google Now
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension Google Network Speech
[8888:1492:1014/133909:VERBOSE1:extension_service.cc(1457)] AddComponentExtension CryptoTokenExtension
[8888:1492:1014/133909:VERBOSE1:app_list_syncable_service.cc(263)] 05949BD0: AppListSyncableService: InitializeWithService.
[8888:1492:1014/133909:VERBOSE1:app_list_syncable_service.cc(775)] 05949BD0: SyncStarted: Flare.
[8888:1492:1014/133909:VERBOSE1:account_reconcilor.cc(209)] AccountReconcilor::AccountReconcilor
[8888:1492:1014/133909:VERBOSE1:account_reconcilor.cc(222)] AccountReconcilor::Initialize
[8888:1492:1014/133909:VERBOSE1:ev_whitelist_component_installer.cc(117)] Registering EV whitelist component.
[8888:1492:1014/133909:VERBOSE1:component_updater_service.cc(265)] CrxUpdateService starting up
[8888:1492:1014/133909:VERBOSE1:startup_browser_creator_impl.cc(591)] StartupBrowserCreatorImpl::ProcessStartupURLs
[8888:1492:1014/133909:VERBOSE1:startup_browser_creator_impl.cc(597)] Pref: urls
[8888:8128:1014/133909:VERBOSE1:ev_whitelist_component_installer.cc(83)] Verifying install: C:\Users\natlessa\AppData\Local\Google\Chrome\User Data\EVWhitelist\1\_platform_specific\all\ev_hashes_whitelist.bin
[8888:8128:1014/133909:VERBOSE1:ev_whitelist_component_installer.cc(95)] Whitelist size: 634842
[8888:8468:1014/133909:VERBOSE1:crl_set_fetcher.cc(103)] Loaded 212062 bytes of CRL set from disk
[8888:8804:1014/133909:VERBOSE1:crl_set_fetcher.cc(125)] Installed CRL set #1857
[8888:1492:1014/133909:VERBOSE1:static_browser_cld_data_provider.cc(19)] Creating StaticBrowserCldDataProvider
[8888:1492:1014/133909:VERBOSE1:one_click_signin_helper.cc(789)] OneClickSigninHelper::CanOffer
[8888:1492:1014/133909:VERBOSE1:one_click_signin_helper.cc(882)] OneClickSigninHelper::CanOffer: yes we can
[1014/133909:VERBOSE1:child_thread.cc(242)] Mojo is disabled on child
[8888:1492:1014/133909:VERBOSE1:one_click_signin_helper.cc(1281)] OneClickSigninHelper::DidStartNavigationToPendingEntry: url=https://www.google.com/
[8888:1492:1014/133909:VERBOSE1:component_updater_service.cc(265)] CrxUpdateService starting up
[8888:1492:1014/133909:VERBOSE1:component_updater_service.cc(272)] First update attempt will take place in 360 seconds
[8888:1492:1014/133909:VERBOSE1:ev_whitelist_component_installer.cc(65)] Component ready, version 1 in C:\Users\natlessa\AppData\Local\Google\Chrome\User Data\EVWhitelist\1
[8888:6632:1014/133909:VERBOSE1:dhcp_proxy_script_adapter_fetcher_win.cc(264)] Error fetching PAC URL from DHCP: 2
[8888:2824:1014/133910:VERBOSE1:dhcp_proxy_script_adapter_fetcher_win.cc(264)] Error fetching PAC URL from DHCP: 2
[8888:7672:1014/133910:VERBOSE1:dhcp_proxy_script_adapter_fetcher_win.cc(264)] Error fetching PAC URL from DHCP: 2
[8888:8280:1014/133910:VERBOSE1:dhcp_proxy_script_adapter_fetcher_win.cc(264)] Error fetching PAC URL from DHCP: 2
[8888:8804:1014/133911:VERBOSE1:proxy_service.cc(1165)] Failed configuring with PAC script, falling-back to manual proxy servers.
[8888:8804:1014/133911:VERBOSE1:proxy_service.cc(1165)] Failed configuring with PAC script, falling-back to manual proxy servers.
[8888:8804:1014/133911:VERBOSE1:ssl_client_socket_nss.cc(3477)] CT Verification complete: result -158 Invalid scts: 0 Verified scts: 0 scts from unknown logs: 0
[8888:8804:1014/133911:VERBOSE1:database_manager.cc(1047)] SafeBrowsingCheckDone
[8888:9088:1014/133919:VERBOSE1:dhcp_proxy_script_adapter_fetcher_win.cc(264)] Error fetching PAC URL from DHCP: 2
[8888:6632:1014/133919:VERBOSE1:dhcp_proxy_script_adapter_fetcher_win.cc(264)] Error fetching PAC URL from DHCP: 2
[8888:8524:1014/133919:VERBOSE1:dhcp_proxy_script_adapter_fetcher_win.cc(264)] Error fetching PAC URL from DHCP: 2
[8888:8280:1014/133919:VERBOSE1:dhcp_proxy_script_adapter_fetcher_win.cc(264)] Error fetching PAC URL from DHCP: 2
[8888:2424:1014/133919:WARNING:process_metrics_history.cc(62)] GetMemoryBytes returned NULL (platform-specific error)
[8888:2424:1014/133919:WARNING:process_metrics_history.cc(62)] GetMemoryBytes returned NULL (platform-specific error)
[8888:2424:1014/133919:WARNING:process_metrics_history.cc(62)] GetMemoryBytes returned NULL (platform-specific error)
[8888:8804:1014/133919:VERBOSE1:bandwidth_metrics.h(95)] Bandwidth: 8906.86Kbps (avg 8906.86Kbps)

[Noel Allen]

Your description doesn't sound like a NaCl related issue, so I assume there's some missing information since you posted to this group.

Are you loading any NaCl Modules?   Perhaps you can capture the process tree, that might give us some insight, maybe you have some packaged apps running in the background?

Have you accidentally left on nacl debugging?

What changed since the last time you ran it?

Have you tried loading with --user-data-dir=  to avoid stale profile/state information?

What the full command-line, are you loading any experimental ppapi modules?

--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-di...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.

[Nathan L.]

On Tuesday, October 14, 2014 2:59:47 PM UTC-7, Noel Allen wrote:

Your description doesn't sound like a NaCl related issue, so I assume there's some missing information since you posted to this group.

Are you loading any NaCl Modules?   Perhaps you can capture the process tree, that might give us some insight, maybe you have some packaged apps running in the background?

Have you accidentally left on nacl debugging?

What changed since the last time you ran it?

Have you tried loading with --user-data-dir=  to avoid stale profile/state information?

What the full command-line, are you loading any experimental ppapi modules?

 

Yes I was loading nacl modules. That's why I posted it on this site. I use the following command for that, so my devel profile/state is separate from my user profile/state.

This is what I use for development:

>chrome --enable-nacl --enable-logging --v=1 --register-pepper-plugins="C:\VisualStudio10Workspace\PNaCl\PNaCl_Module\win\PNaCl_Module.dll";application/x-ppapi http://localhost:5103 --no-sandbox --user-data-dir="C:\NaCl_SDK\logs\chrome_data"

Working case:

>chrome --no-sandbox

Not working case:

>chrome

You are right though the symptoms were as if Chrome was left in debugging waiting for GDB. But I checked the flag and it’s not enabled. Whatever it is has persisted an uninstall/reinstall of Chrome!

 

How would you recommend I capture the process tree?

Thanks,

 

To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsub...@googlegroups.com.

[Nick Bray]

Environment variables?  If you're redirecting stdout, this could be causing problems without --no-sandbox.  Also see if there's any NaCl-specific stuff that somehow persisted in about:flags.

To unsubscribe from this group and stop receiving emails from it, send an email to native-client-di...@googlegroups.com.

[Noel Allen]

This is what I use for development:

>chrome --enable-nacl --enable-logging --v=1 --register-pepper-plugins="C:\VisualStudio10Workspace\PNaCl\PNaCl_Module\win\PNaCl_Module.dll";application/x-ppapi http://localhost:5103 --no-sandbox --user-data-dir="C:\NaCl_SDK\logs\chrome_data"

You are registering a pepper plugin (DLL).  So perhaps you are not using NaCl at all and just PPAPI?

If that's the case, then the --no-sandbox is allowing you access to Win32 API functions that you can't get to without.  I suspect his is causing your lockup.

-Noel

[Nathan L.]

The problem went away! I’m not sure how, but its gone!

 

However, I think I found out how to reproduce the problem or at least the symptoms of it. If you try to load a PPAPI plugin which accesses sandboxed code (e.g. native file I/O) without the –no-sandbox flag, it causes Chrome’s topmost process to lockup and be unresponsive. The first tab with say “Loading …” and keeps spinning. You can open a new tap, but you can’t load any URLs including “about:flags” in the new tab.

 

The difference is that now, I I open a new instance of Chrome (topmost process), it works fine and can access valid URLs as expected without the –no-sandbox flag. Before when I had the original problem, even a new instances of Chrome was unresponsive without the –no-sandbox flag!

I guess that’s what you were suspecting the issue was also. But I was expecting Chrome to complain about security violation or some other informative message, or at least allow me to enter the developer tools, rather than just hang silently!

To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsubscri...@googlegroups.com.

To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-discuss+unsub...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss.
For more options, visit https://groups.google.com/d/optout.