Issue 1989723003: Use a reader-writer lock to protect the threads table in BrowserThreadImpl.

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

Issue 1989723003: Use a reader-writer lock to protect the threads table in BrowserThreadImpl.

Created:
4 years, 7 months ago by Anand Mistry (off Chromium)

Modified:
4 years, 6 months ago

Reviewers:

CC:
chromium-reviews, darin-cc_chromium.org, jam

Base URL:
https://chromium.googlesource.com/chromium/src.git@rw-lock-incoming-task-queue

Target Ref:
refs/pending/heads/master

Project:
chromium

Visibility:
Public.

More Reviews

Description

Use a reader-writer lock to protect the threads table in BrowserThreadImpl. If |lock| is being held while posting the task to the task runner, and the posting results in the thread being switched out, any other thread that tries to use BrowserThread to post a task will be blocked while trying to acquire |lock|.

Patch Set 1 #

Patch Set 2 : Rebase #

Patch Set 3 : Rebase #

Created: 4 years, 6 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+13 lines, -12 lines)			Patch
	M	content/browser/browser_thread_impl.cc	View	1	12 chunks	+13 lines, -12 lines	0 comments	Download

Depends on Patchset:

Issue 1991623002 Patch 80001