base/message_loop.cc - Issue 6676099: When we process the tickler message in our windows message pump, we should not dispatch

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: base/message_loop.cc

Issue 6676099: When we process the tickler message in our windows message pump, we should not dispatch (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/

Patch Set: '' Created 9 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

Index: base/message_loop.cc

===================================================================

--- base/message_loop.cc (revision 78988)

+++ base/message_loop.cc (working copy)

@@ -123,6 +123,9 @@

nestable_tasks_allowed_(true),

exception_restoration_(false),

state_(NULL),

+#ifdef OS_WIN

+ os_modal_loop_(false),

+#endif // OS_WIN

next_sequence_num_(0) {

DCHECK(!current()) << "should only have one message loop per thread";

lazy_tls_ptr.Pointer()->Set(this);

« no previous file with comments | « base/message_loop.h ('k') | base/message_pump_win.cc » ('j') | no next file with comments »