Native logs are not uploaded on device Parrot |
|||
Issue descriptionChrome Version: M52 (52.0.2723.0 / 8276.0.0 dev) Device : Parrot What steps will reproduce the problem? 1. Join a hangout call from device Parrot and another machine(desktop) 2. Complete the call 3. Go to chrome://webrtc-logs 4. Open "filesystem:https://plus.google.com/temporary/log_v2/" in another tab Expected result: 1. Webtrc logs should be captured (local file should be generated and log file should be uplaoded) in chrome://webrtc-logs 2. Hangout entry should be displayed in "filesystem:https://plus.google.com/temporary/log_v2/" and relevant hangout js log file should be generated Actual result: 1. Webtrc logs are not captured (local file is not generated and log file is not uplaoded) in chrome://webrtc-logs 2. Hangout entry is not displayed in "filesystem:https://plus.google.com/temporary/log_v2/" and relevant hangout js log file are not generated Notes: 1. Hangout calls were made between two corp accounts 2. This issue is also seen in M50 stable and M51 beta versions chrome://webrtc-logs : No log file is uploaded but local file was generated in native logs No entry for hangout call in filesystem
,
May 9 2016
tnkamura@: Retested hangouts on device Parrot with M51 51.0.2704.37 / 8172.25.0 beta. After the hangout call, only local file is generated and no logs are uploaded. There is an entry in "filesystem:https://plus.google.com/temporary/log_v2/" a) "Report additional diagnostics to help improve hangouts" checkbox is checked in Hangout settings b) Submitted hangouts feedback. Native Logs are not uploaded. c) Base URL for hangouts is : https://hangouts.google.com/hangouts/_/google.com/meetingname Please find attached js logs for the hangout between device Parrot and desktop(Linux). Observed following lines in js logs: "[79.373s]10 Error(talk.media.webrtc.FluteSession): Transport writable timeout failed, aborting. [79.374s]8 talk.media.webrtc.FluteSession: Sending ["fe","muvc-private-chat-99996quikjryofbfvjte3v5jx6kwoae@groupchat.google.com","c881337946428559724_NMS","1"] [79.405s]3 talk.media.webrtc.TalkWebRtc: Asked to send message: ["jt","muvc-private-chat-99996quikjryofbfvjte3v5jx6kwoae@groupchat.google.com","c881337946428559724_NMS",55] [79.407s]8 talk.media.webrtc.FluteSession: Recving ["jt","muvc-private-chat-99996quikjryofbfvjte3v5jx6kwoae@groupchat.google.com","c881337946428559724_NMS",55,null] [79.407s]8 talk.media.webrtc.FluteSession: Sending ["jmiend","muvc-private-chat-99996quikjryofbfvjte3v5jx6kwoae@groupchat.google.com","c881337946428559724_NMS",56,true,0] [79.421s]3 talk.media.webrtc.TalkWebRtc: Deleted session with remoteJid=muvc-private-chat-99996quikjryofbfvjte3v5jx6kwoae@groupchat.google.com and sessionId=c881337946428559724_NMS [79.422s]3 talk.media.webrtc.TalkWebRtc: Stopping logs. [79.422s]8 talk.media.webrtc.Extension: Sending message {"method":"logging.stop"} [79.429s]8 talk.media.webrtc.Extension: Sending message {"method":"logging.stopRtpDump","incoming":true,"outgoing":true} [79.433s]9 Warning(talk.media.webrtc.OutputTracker): recordBeforeAudioStop: No info found for ssrc 8579373 [79.465s]8 talk.media.webrtc.FluteSession: ICE connection state changed to: closed [79.466s]8 talk.media.webrtc.Extension: Received response to logging.stop: null [79.466s]3 talk.media.webrtc.TalkWebRtc: Native log stopped. [79.471s]8 talk.media.webrtc.Extension: Sending message {"method":"logging.store","logId":"c881337946428559724_NMS"} [79.498s]3 talk.media.webrtc.TalkWebRtc: Asked to send message: ["comment","Relaying plugin message to WCS: jmiend"] [79.520s]3 talk.media.webrtc.FluteSession: send datachannel is closed. [79.526s]8 talk.media.webrtc.Extension: Received response to logging.stopRtpDump: null [79.552s]8 talk.media.webrtc.Extension: Received response to logging.store: null" Note: Observed that native and js logs are generated as expected for another hangout call which had a duration of roughly 10-15min on device Parrot with same M51 beta build (51.0.2704.37 / 8172.25.0 beta)
,
May 10 2016
> There is an entry in "filesystem:https://plus.google.com/temporary/log_v2/" I think you mean filesystem:https://hangouts.google.com/temporary/log_v2/ ? Please file an internal Hangouts bug for the failing native log upload.
,
May 10 2016
Yes. I meant "filesystem:https://hangouts.google.com/temporary/log_v2/"
,
May 10 2016
Filed https://b.corp.google.com/issues/28691909. Closing this issue as per comment#3. |
|||
►
Sign in to add a comment |
|||
Comment 1 by tnakamura@chromium.org
, May 9 2016Labels: -Pri-3 Needs-Feedback Pri-1