FS#60258 - [chromium] Continuous spamming GetVSyncParametersIfAvailable() failed!

Attached to Project: Arch Linux
Opened by Henrique (hdante) - Sunday, 30 September 2018, 23:01 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 17 March 2019, 02:26 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
Looking at my journal, chromium started spamming the following error on July 30th:

set 30 19:56:15 dragonmount chromium.desktop[890]: [6297:6297:0930/195615.046891:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!

It's logging this nonstop. Currently grepping the journal for GetVSyncParametersIfAvailable results in a 154 MB file.


Additional info:
* package version(s)
chromium 69.0.3497.100-1

* config and/or log files etc.
Same bug reported in debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901831


Steps to reproduce:
Run chromium and it starts happening.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Sunday, 17 March 2019, 02:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  chromium 73.0.3683.75-1 contains the upstream fix for the log spam; if you're using Chrome, obviously it won't apply there...
Comment by Henrique (hdante) - Sunday, 30 September 2018, 23:20 GMT
Note: the problem is hidden when I configure chromium in the settings page not to use hardware acceleration
Comment by Mark Blakeney (bulletmark) - Saturday, 16 March 2019, 00:44 GMT
  • Field changed: Percent Complete (100% → 0%)
Sorry, but 73.0.3683.75-1 doesn't seem to make any difference. Still as much GetVSyncParametersIfAvailable() spam as ever.
Comment by Evangelos Foutras (foutrelis) - Saturday, 16 March 2019, 00:53 GMT
So the backported fix from https://crbug.com/879929 doesn't help? What's the exact log spam currently?

Looking at the code, it seems to log a warning the first 19 times GetVSyncParametersIfAvailable() fails, and then once every 256 times. This should greatly limit the number of times it gets logged.
Comment by Mark Blakeney (bulletmark) - Sunday, 17 March 2019, 01:48 GMT
E.g. simply opening a tab and scrolling around generates about 50 journal messages per second. Still seems ridiculously excessive to me. Sample messages are:

Mar 17 11:41:16 lt google-chrome.desktop[1112]: [1730:1730:0317/114116.253053:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Mar 17 11:41:16 lt google-chrome.desktop[1112]: [1730:1730:0317/114116.443636:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Mar 17 11:41:16 lt google-chrome.desktop[1112]: [1730:1730:0317/114116.452934:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Mar 17 11:41:16 lt google-chrome.desktop[1112]: [1730:1730:0317/114116.460306:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Mar 17 11:41:16 lt google-chrome.desktop[1112]: [1730:1730:0317/114116.470212:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Mar 17 11:41:16 lt google-chrome.desktop[1112]: [1730:1730:0317/114116.477351:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Mar 17 11:41:16 lt google-chrome.desktop[1112]: [1730:1730:0317/114116.486819:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed!
Comment by Evangelos Foutras (foutrelis) - Sunday, 17 March 2019, 02:24 GMT
google-chrome.desktop? google-chrome.desktop????? google-chrome.desktop??????????????????????

Loading...