New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 690376 link

Starred by 1 user
Status: Assigned
Owner:
nisse@chromium.org
Cc:
nisse@chromium.org
█ danilchap@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

log spam during hangout: rtp_utility.cc(337): Failed to find extension id: 3

Project Member Reported by djkurtz@chromium.org, Feb 9 2017 
Chrome Version: 56.0.2924.79
Chrome OS Version: 9000.76.0
Chrome OS Platform: elm

Steps To Reproduce:
(1) Join a hangout video conference
(2) Inspect /var/log/chrome/chrome
(3)

Expected Result:

No log spam in CHROME_SYSTEM_LOG (/var/log/chrome/chrome).

Actual Result:

[1:44:0203/160604.260193:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.273386:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.274548:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.292079:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.292967:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.319598:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.322138:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.332653:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.332963:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.354001:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3
[1:44:0203/160604.356967:WARNING:rtp_utility.cc(337)] Failed to find extension id: 3

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

Always

What is the impact to the user, and is there a workaround? If so, what is
it?

Unknown.

Please provide any additional information below. Attach a screen shot or
log if possible.

Comment 1 by djkurtz@google.com, Feb 9 2017 

Not that those messages are only milliseconds apart - there are like 100 of these messages / second.

Comment 2 by nisse@chromium.org, Oct 23 2017

Cc: nisse@chromium.org
Is this still happening? Deleting the log message should be easy, but I guess it was added on the theory that it shouldn't happen if extensions are properly configured and negotiated.
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 23

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by guidou@chromium.org, Nov 16

Owner: nisse@chromium.org
Status: Assigned (was: Untriaged)
nisse@: Is this still an issue?

Comment 5 by nisse@chromium.org, Nov 16

Cc: danilchap@chromium.org
We will still log one message per rtp packet if we get packets with rtp extensions we don't expect. If it still happens with hangouts, I don't know.

Would make sense to me to demote the log message from LS_WARNING to LS_INFO.
►

Sign in to add a comment