Issue metadata
Sign in to add a comment
|
Each time google-chrome-stable runs, syslog fills up with error messages.
Reported by
kfar...@gmail.com,
Apr 10 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 Steps to reproduce the problem: 1. Install Chrome 65.0.3325.181 (Official Build) (64-bit) on Ubuntu 17.10 (up to date patches) 2. Start google-chrome-stable from icon/menu 3. watch syslog for errors like: Apr 10 12:51:18 ardita google-chrome.desktop[29670]: [29839:29839:0410/125118.373409:ERROR:gl_surface_presentation_helper.cc(104)] GetVSyncParametersIfAvailable() failed! You can also run from command line and get same errors for a while, then get these errors: : default value of option force_s3tc_enable overridden by environment. [27747:27747:0410/125017.361933:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool) [27747:27784:0410/125018.209494:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &) [27747:27784:0410/125019.151091:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &) [27747:27784:0410/125019.167647:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &) [27747:27784:0410/125019.169345:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &) [27747:27784:0410/125019.240369:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &) [27747:27747:0410/125019.335121:ERROR:CONSOLE(6)] "Uncaught ReferenceError: gbar is not defined", source: https://clients5.google.com/pagead/drt/dn/ (6) What is the expected behavior? That when running google-chrome-stable it doesn't fill up the syslog with things like: Apr 10 12:51:18 ardita google-chrome.desktop[29670]: [29839:29839:0410/125118.373409:ERROR:gl_surface_presentation_helper.cc(104)] GetVSyncParametersIfAvailable() failed! Literally thousands of lines if left to run and you do anything with Chrome. What went wrong? While the browser does work, syslog is a fast and constant stream of error messages, literally thousands, as fast as they can scroll up the terminal window. Did this work before? N/A Chrome version: 65.0.3325.181 (Official Build) (64-bit) Channel: stable OS Version: 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Flash Version: Shockwave Flash 29.0 r0 I only today realized this behavior started back as far as March 29. It could be longer, but all my syslogs have rolled. The gl_surface_presentation_helper.cc error message was logged 28411 times in my oldes syslog.7.gz file.
,
Apr 15 2018
Chromium Version 65.0.3325.181 (Official Build) Arch Linux (64-bit) I noticed that I get 4 upload_data_presenter.cc error every time i open a new tab loading the "new tab" page. Reloading the "new tab" page results with another 4 errors each time. chromium.desktop[19978]: [19978:20009:0415/115856.445856:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &) Not clogging syslog but my systemd-journal.
,
Apr 16 2018
Ubuntu 16.04.4 LTS Version 65.0.3325.181 (Official Build) I have this problem too. In /var/log/syslog: ERROR:gl_surface_presentation_helper.cc(104)] GetVSyncParametersIfAvailable() failed! Everytime then I click on tab.
,
Apr 18 2018
It looks like the upload_data_presenter.cc error is fixed in Version 66.0.3359.117 (Official Build) Arch Linux (64-bit)
,
Apr 19 2018
@Reporter: As per comment#4, Could you please try to test this issue on latest chrome stable# 66.0.3359.117 and let us know if the issue still persists. You can download chrome latest stable from URL: https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
Apr 19 2018
I just updated to latest Chrome, 66.0.3359.117 and that cleared the streaming syslog errors. You can probably close this bug with the solution to update to the newer version. Here's my new version info that cleared the issue: Google Chrome 66.0.3359.117 (Official Build) (64-bit) Revision 7f59c28e25283df88e0c6ac8d8b2551d8c6ad93b-refs/branch-heads/3359@{#723} OS Linux JavaScript V8 6.6.346.24 Flash 29.0.0.113 /home/kfarley/.config/google-chrome/PepperFlash/29.0.0.113/libpepflashplayer.so User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Command Line /usr/bin/google-chrome-stable --flag-switches-begin --flag-switches-end Executable Path /opt/google/chrome/google-chrome Just because you might be interested, these are the errors that I get on launch of that version, not a big deal, I can ignore these. Apr 19 08:46:21 ardita org.gnome.Shell.desktop[3178]: [24855:24883:0419/084621.115802:ERROR:in_progress_cache_impl.cc(93)] Could not read download entries from file because there was a read failure. Apr 19 08:46:21 ardita org.gnome.Shell.desktop[3178]: ATTENTION: default value of option force_s3tc_enable overridden by environment. Apr 19 08:46:21 ardita org.gnome.Shell.desktop[3178]: [24855:24855:0419/084621.282509:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool) Apr 19 08:46:21 ardita gnome-shell[3178]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.163/org/ayatana/NotificationItem/chrome_app_indicator_1 Apr 19 08:46:23 ardita org.gnome.Shell.desktop[3178]: [24855:24855:0419/084623.594808:ERROR:CONSOLE(6)] "Uncaught ReferenceError: gbar is not defined", source: https://clients5.google.com/pagead/drt/dn/ (6)
,
Apr 19 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 20 2018
As per comment#6 from the reporter, closing the issue and marking it as Won't fix. Thanks! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Apr 10 2018