New issue
Advanced search Search tips

Issue 771793 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

FATAL:profile_destroyer.cc(56)] Check failed: hosts.empty() || profile->IsOffTheRecord() || content::RenderProcessHost::run_renderer_in_process(). Profile still has 1 hosts

Project Member Reported by elawrence@chromium.org, Oct 4 2017

Issue description

Chrome Version: ToT 63

What steps will reproduce the problem?
(1) Build Chromium
(2) Open http://webdbg.com/test/forms/annoy.html
(3) Type a character in the password box 
(4) Tick the checkbox
(5) Hit F12 to open the Developer Tools, go to Security tab
(6) Attempt to close the top-level Chrome window via the Red-X

---------------------------
Fatal error
---------------------------
[3316:6352:1004/172428.903:FATAL:profile_destroyer.cc(56)] Check failed: hosts.empty() || profile->IsOffTheRecord() || content::RenderProcessHost::run_renderer_in_process(). Profile still has 1 hosts
Backtrace:
	base::debug::StackTrace::StackTrace [0x100BFC56+102]
	base::debug::StackTrace::StackTrace [0x100BEED3+35]
	logging::LogMessage::~LogMessage [0x101343C5+149]
	ProfileDestroyer::DestroyProfileWhenAppropriate [0x1627E54F+1087]
	ProfileManager::ProfileInfo::~ProfileInfo [0x1612D0DC+28]
	std::default_delete<ProfileManager::ProfileInfo>::operator() [0x1612D096+38]
	std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> >::~unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> > [0x161217ED+61]
	std::pair<base::FilePath const ,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> > >::~pair<base::FilePath const ,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> > > [0x161264BB+27]
	std::_Default_allocator_traits<std::allocator<std::_Tree_node<std::pair<base::FilePath const ,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> > >,void *> > >::destroy<std::pair<base::FilePath const ,std::unique [0x161263CC+28]
	std::_Tree<std::_Tmap_traits<base::FilePath,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> >,std::less<base::FilePath>,std::allocator<std::pair<base::FilePath const ,std::unique_ptr<ProfileManager::ProfileInfo [0x161261DC+124]
	std::_Tree<std::_Tmap_traits<base::FilePath,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> >,std::less<base::FilePath>,std::allocator<std::pair<base::FilePath const ,std::unique_ptr<ProfileManager::ProfileInfo [0x16125608+56]
	std::_Tree<std::_Tmap_traits<base::FilePath,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> >,std::less<base::FilePath>,std::allocator<std::pair<base::FilePath const ,std::unique_ptr<ProfileManager::ProfileInfo [0x16125403+211]
	std::_Tree<std::_Tmap_traits<base::FilePath,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> >,std::less<base::FilePath>,std::allocator<std::pair<base::FilePath const ,std::unique_ptr<ProfileManager::ProfileInfo [0x16125278+152]
	std::_Tree<std::_Tmap_traits<base::FilePath,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> >,std::less<base::FilePath>,std::allocator<std::pair<base::FilePath const ,std::unique_ptr<ProfileManager::ProfileInfo [0x161251C4+20]
	std::map<base::FilePath,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete<ProfileManager::ProfileInfo> >,std::less<base::FilePath>,std::allocator<std::pair<base::FilePath const ,std::unique_ptr<ProfileManager::ProfileInfo,std::default_delete [0x161116FF+15]
	ProfileManager::~ProfileManager [0x16138319+313]
	ProfileManager::`scalar deleting destructor' [0x16122E45+37]
	std::default_delete<ProfileManager>::operator() [0x131236E5+53]
	std::unique_ptr<ProfileManager,std::default_delete<ProfileManager> >::reset [0x13114037+87]
	BrowserProcessImpl::StartTearDown [0x131136CF+1391]
	ChromeBrowserMainParts::PostMainMessageLoopRun [0x1305B5DB+779]
	content::BrowserMainLoop::ShutdownThreadsAndCleanUp [0x08B0C7CA+1162]
	content::BrowserMainRunnerImpl::Shutdown [0x08B1DD20+1696]
	content::BrowserMain [0x08AFF4F2+226]
	content::RunNamedProcessTypeMain [0x0BA76DD1+209]
	content::ContentMainRunnerImpl::Run [0x0BA77E02+674]
	content::ContentServiceManagerMainDelegate::RunEmbedderProcess [0x0BA75F41+33]
	service_manager::Main [0x27E861CE+1534]
	content::ContentMain [0x0BA76C4A+74]
	ChromeMain [0x10AA74E5+501]
	MainDllLoader::Launch [0x004303CA+1178]
	wWinMain [0x00422FC2+1362]
	invoke_main [0x006AB54E+30] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:123)
	__scrt_common_main_seh [0x006AB3C0+336] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:283)
	__scrt_common_main [0x006AB25D+13] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:326)
	wWinMainCRTStartup [0x006AB5C8+8] (f:\dd\vctools\crt\vcstartup\src\startup\exe_wwinmain.cpp:17)
	BaseThreadInitThunk [0x772762C4+36]
	RtlSubscribeWnfStateChangeNotification [0x77DE0F79+1081]
	RtlSubscribeWnfStateChangeNotification [0x77DE0F44+1028]
	(No symbol) [0x00000000]


---------------------------
OK   
---------------------------



 
Owner: elawrence@chromium.org
Thank you for your report!

Can you please clarify a couple of things?
1. Which OS & build flags did you use?
2. By "Red-X" you mean regular "window close" button, don't you?
1. Windows 10:
is_clang = true        
is_win_fastlink = true    
is_component_build = true 
target_cpu = "x86"
symbol_level = 1                   
enable_nacl = false                
remove_webcore_debug_symbols = true

2. Yes, the "window close" button at the top-right side of the UI.

Notably, I cannot reproduce this problem today at ToT (c04824a55de8f93c344eeed2aaa9918068203b1e) so perhaps this was fixed in the last 10 days?
Mergedinto: 496653
Status: Duplicate (was: Untriaged)
To be honest, I don't know whether it was fixed by any of the recent changes, as ProfileDestroyer error may be triggered by anything that causes RenderProcessHosts to hang.

I'm marking this as a duplicate of issue 496653. If you encounter this issue again - please post a comment there.

Sign in to add a comment