New issue
Advanced search Search tips

Issue 842646 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug


Previous locations:
webrtc:9233


Sign in to add a comment

Video orientation from iOS client is incorrect in Chrome 67

Reported by yu...@appear.in, May 3 2018

Issue description

What steps will reproduce the problem?
1. Join AppRTC room from Chrome 67 (beta)
2. Join the same room from AppRTC client on iOS

What is the expected result?
Video received from iOS client in Chrome is rotated correctly according to iOS device orientation.

What do you see instead?
Video received from iOS client in Chrome is rotated sideways when iOS client is in portrait. Orientation doesn't change at all when iOS device is rotated.

What version of the product are you using? On what operating system?
Desktop: 
macOS 10.13.4 (17E202)
Chrome Version 67.0.3396.30 (Official Build) beta (64-bit)

iOS: 11.3.1 (15E302)
AppRTC build from latest commit in master: a1f566b28a69512037e36f5194329d9ada46be01


Please provide any additional information below.
WebRTC internals dump attached.
Works as expected in Chrome 66.

 
webrtc_internals_dump.txt
297 KB View Download

Comment 1 by fi...@appear.in, May 3 2018

works in Chrome 66.0.3359.139
broken in 67.0.3396.30 and 68.0.3409.2

happy bisect

Comment 2 by fi...@appear.in, May 3 2018

also reproducible with the appear.in and talky.io apps ios apps.
Makes it looks like the other person useds Konrads Kalasklister ;-)
Components: Mobile Video

Comment 4 by fi...@appear.in, May 4 2018

Google Chrome 67.0.3371.0 (which used to be unstable at some point) still shows the correct behaviour.

Comment 5 by fi...@appear.in, May 4 2018

bad: 67.0.3396.18
bad: 67.0.3386.1
good: 67.0.3381.0

Looking at https://chromium.googlesource.com/chromium/src/+log/67.0.3381.0..67.0.3386.0?pretty=fuller&n=10000
and taking the autoroller commit hashes I get https://webrtc.googlesource.com/src.git/+log/dc4737bbdacc..0ffe03d2ef6f I don't see anything suspicious offhand.

Comment 6 by sakal@webrtc.org, May 4 2018

Cc: kthelgason@webrtc.org
Labels: OS-iOS
Does this repro when receiving video from Android?

Comment 7 by stefan@webrtc.org, May 4 2018

Owner: sakal@webrtc.org
Status: Assigned (was: Unconfirmed)
Setting you as owner Sami since you seem to be on top of this right now.

Comment 8 by sakal@webrtc.org, May 4 2018

Labels: Needs-Feedback

Comment 9 by fi...@appear.in, May 6 2018

not from Chrome 66 on android from what I can see.

Chrome 68.0.3418.2 seems to fix this so there are now two bisect windows :-)

Comment 10 by sakal@webrtc.org, May 7 2018

Does the version of AppRTCMobile on iOS matter? If not, this is probably not mobile bug?

Comment 11 by fi...@appear.in, May 7 2018

since it changes with Chrome version i'd say its a problem on that side. Throw it over to gui-"master of bisect"-do? :-)

Comment 12 by yu...@appear.in, May 7 2018

Also reproducible with AppRTCMobile on iOS built from older stable branch 64. I agree that looks like the problem is on Chrome side.

Comment 13 by sakal@webrtc.org, May 7 2018

Components: -Mobile
Labels: -OS-iOS OS-Mac
Owner: ----
Status: Untriaged (was: Assigned)
Unassigning for a new triage. This should probably be assigned to someone working with WebRTC on Mac.

Comment 14 by sakal@webrtc.org, May 7 2018

Cc: sakal@webrtc.org

Comment 15 by guidou@webrtc.org, May 7 2018

Cc: chfremer@webrtc.org
Owner: kthelgason@webrtc.org
Status: Assigned (was: Untriaged)
kthelgason@, could you find a suitable owner for this?
Owner: guidou@webrtc.org
This is not a bug in WebRTC iOS, more likely on the chrome side.

Guido, can you help this issue find its rightful onwer?
Project: chromium
Moved issue webrtc:9233 to now be  issue chromium:842646 .

Comment 19 by guidou@webrtc.org, May 14 2018

Cc: guidou@chromium.org
Components: Blink>WebRTC>Video
Owner: ----
Status: Untriaged (was: Assigned)
Cc: -chfremer@webrtc.org chfremer@chromium.org

Comment 21 by fi...@appear.in, May 14 2018

apparently fixed between 67.0.3396.30 (bad) and 67.0.3396.40 which reduces priority to "why did this break?"
Cc: emir...@chromium.org
Status: Fixed (was: Untriaged)
Given comment #21 that it has been already been fixed and the difficulty of finding anyone willing to own it, I'll close this bug. Please reopen if needed.
https://chromium-review.googlesource.com/c/chromium/src/+/1036605 probably fixed it. GpuMemoryBufferVideoFramePool wasn't preserving rotation information.

Sign in to add a comment