New issue
Advanced search Search tips

Issue 655703 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: Aug 21
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

When connecting via Chrome Remote Desktop - FATAL: screen_win_displays_.size() == 0u (1 vs. 0)

Project Member Reported by elawrence@chromium.org, Oct 13 2016

Issue description

Version: 56.0.2880.0
OS: Win7

What steps will reproduce the problem?
(1) Open debug Chromium instance on a PC
(2) Use Chrome Remote Desktop to connect to that PC

---------------------------
Fatal error
---------------------------
[9792:9368:1012/182925:FATAL:screen_win.cc(565)] Check failed: screen_win_displays_.size() == 0u (1 vs. 0)
Backtrace:
	base::PersistentHistogramAllocator::Id [0x1007B987+336371]
	base::PersistentHistogramAllocator::Id [0x100CADCB+661047]
	display::ResetDisplayIdForTest [0x0D8C65DD+332016]
	display::ResetDisplayIdForTest [0x0D8C6A17+333098]
	display::ResetDisplayIdForTest [0x0D8C5C7F+329618]
	aura::client::ScreenPositionClient::operator= [0x15CDC3A1+229328]
	aura::client::ScreenPositionClient::operator= [0x15CDCEBC+232171]
	views::HWNDMessageHandler::HasCapture [0x3868A837+1977673]
	views::HWNDMessageHandler::HasCapture [0x3861C2F0+1525762]
	views::HWNDMessageHandler::HasCapture [0x38622642+1551188]
	views::HWNDMessageHandler::HasCapture [0x3861280E+1486112]
	views::HWNDMessageHandler::HasCapture [0x38623023+1553717]
	gfx::Transform::operator*= [0x018398D1+886209]
	gfx::Transform::operator*= [0x018377E6+877782]
	gapfnScSendMessage [0x764862FA+818]
	GetDC [0x76487316+82]
	GetThreadDesktop [0x76486DE8+389]
	LoadStringW [0x76488FA7+238]
	KiUserCallbackDispatcher [0x77C3011A+46]
	(No symbol) [0x70EE0E77]
	GetDC [0x764872FC+56]
	CharPrevW [0x764877C4+312]
	DispatchMessageW [0x7648788A+15]
	base::PersistentHistogramAllocator::Id [0x10103EFF+894827]
	base::PersistentHistogramAllocator::Id [0x101040F1+895325]
	base::PersistentHistogramAllocator::Id [0x10102AB2+889630]
	base::PersistentHistogramAllocator::Id [0x1010479B+897031]
	base::PersistentHistogramAllocator::Id [0x100FA86C+856280]
	base::PersistentHistogramAllocator::Id [0x1019E9B4+1528352]
	policy::PolicyDetails::operator= [0x04AD6D35+23710527]
	IPC::MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void>::~MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void> [0x1160362D+15632204]
	IPC::MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void>::~MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void> [0x11608FBF+15655134]
	IPC::MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void>::~MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void> [0x115F6ECB+15581162]
	IPC::MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void>::~MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void> [0x12EB03E7+41506054]
	IPC::MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void>::~MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void> [0x12EB02A8+41505735]
	IPC::MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void>::~MessageT<ScreenOrientationMsg_LockSuccess_Meta,std::tuple<int>,void> [0x12EAE084+41496995]
	policy::PolicyDetails::operator= [0x036E3E22+2792492]
	policy::PolicyDetails::operator= [0x0042E00F+114020]
	policy::PolicyDetails::operator= [0x00428E1C+93041]
	policy::PolicyDetails::operator= [0x004C7FEE+744771]
	policy::PolicyDetails::operator= [0x004C7E50+744357]
	policy::PolicyDetails::operator= [0x004C7CED+744002]
	policy::PolicyDetails::operator= [0x004C8008+744797]
	BaseThreadInitThunk [0x765D336A+18]
	RtlInitializeExceptionChain [0x77C59902+99]
	RtlInitializeExceptionChain [0x77C598D5+54]


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

 

Comment 1 by girard@chromium.org, Apr 19 2017

Note that this is a dcheck

Also happens to me when a display gets removed during suspend/restore.
Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been actively assigned in over a year.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment