Issue 2154783002: Fix bug where a connection switch causes BWE to be set to zero.

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 2154783002: Fix bug where a connection switch causes BWE to be set to zero. (Closed)

Created:
4 years, 5 months ago by honghaiz3

Modified:
4 years, 5 months ago

Reviewers:
tommi, sprang_webrtc, stefan-webrtc

CC:
webrtc-reviews_webrtc.org

Base URL:
https://chromium.googlesource.com/external/webrtc.git@53

Target Ref:
refs/pending/branch-heads/53

Project:
webrtc

Visibility:
Public.

Fix bug where a connection switch causes BWE to be set to zero. BUG=webrtc:6076, 628084 R=sprang@webrtc.org,stefan@webrtc.org TBR=tommi@webrtc.org patch from issue: Review URL: https://codereview.webrtc.org/2125523004 . (cherry picked from commit be40296ccef50dd79312c6fce533bfa36b7063dc) Cr-Commit-Position: refs/branch-heads/53@{#3} Cr-Branched-From: 65f47275cbb5ad3aa5146b9e75afa9894467daff-refs/heads/master@{#13317} Committed: https://chromium.googlesource.com/external/webrtc/+/0c54eb178003a7af9f275429205fea483c1d2578

Created: 4 years, 5 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+54 lines, -1 line)			Patch
	M	webrtc/call/call.cc	View		1 chunk	+6 lines, -1 line	0 comments	Download
	M	webrtc/video/video_send_stream_tests.cc	View		1 chunk	+48 lines, -0 lines	0 comments	Download

Total messages: 2 (1 generated)

honghaiz3

4 years, 5 months ago (2016-07-15 15:23:10 UTC) #2

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
0c54eb178003a7af9f275429205fea483c1d2578.