Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graphic glitches on YouTube: typing lags, scrolling notifications not smooth #79

Closed
scrutinizer11 opened this issue Aug 10, 2022 · 5 comments

Comments

@scrutinizer11
Copy link

Describe the bug

  • Typing text in the comment box (as OP or in reply to another comment) is plagued by a significant lag.
  • Scrolling the notification drop-down menus displays broken graphics (see the video)

To Reproduce
Steps to reproduce the behavior:
induced from the bug description.

Screenshots
https://streamable.com/zy8y58

Desktop (please complete the following information):

  • OS: macOS X Lion
  • Build 104.0.5112.79
@scrutinizer11 scrutinizer11 added the bug Something isn't working label Aug 10, 2022
@Wowfunhappy
Copy link

I'm not convinced that scrolling behavior is a bug. Chromium Legacy is using software rendering, so there's going to be some jelly scrolling on occasion.

@scrutinizer11
Copy link
Author

I enabled hardware acceleration. Firefox Legacy (last updated in Jan 2021) is more capable on some heavy sites than this Chromium thing including YouTube where I have neither the problems mentioned nor a heap of strange inconsistencies at the basic level. FF's UX and UI are better and so is its toolset, so if not for some sites that dropped support such as Github and some discourse-based ones, I'd keep on relying exclusively on FF Legacy.

@Wowfunhappy
Copy link

Chromium Legacy does not support any hardware acceleration on 10.7/8, and it supports very limited acceleration (no gpu compositing) on 10.9. This is regardless of whether "use hardware acceleration when available" is enabled in Chromium settings. (Note the words "when available". 🙂)

Please remember that Chromium Legacy is maintained by a single developer in their spare time, plus a couple of people like me who do our best to help him triage bugs.

@scrutinizer11
Copy link
Author

Ok, and what about a typing lag?

@blueboxd
Copy link
Owner

Pure-performance issues without rendering glitches or malfunctions are not a bug but a restriction of this project.
As mentioned by Wowfunhappy, Chromium cannot use GPU assists due to a lack of support for our old OpenGL.
Theoretically, it may be possible to forward-port old graphics engines' (skia/angle) support logic, but I have no skills in that.

If there're some profiles/traces illustrate these bottlenecks (I cannot replicate this in my env), we can investigate this issue slightly more, but unless who is familiar with this field is willing to help, there is not much hope for a solution.

@blueboxd blueboxd closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2022
@blueboxd blueboxd removed the bug Something isn't working label Aug 18, 2022
blueboxd pushed a commit that referenced this issue Aug 31, 2022
Change-Id: I60e2a0ed2e3d10cb945b4acdc47ab2238d5c5149
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3783167
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5195@{#79}
Cr-Branched-From: 7aa3f07-refs/heads/main@{#1027018}
blueboxd pushed a commit that referenced this issue Sep 29, 2022
https://chromium.googlesource.com/v8/v8.git/+log/83c18f0ee52b..315776a366f0

2022-08-24 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Version 10.6.194.7
2022-08-24 jkummerow@chromium.org Revert "[ptr-compr][turbofan][x64] Support pointer decompressing by"

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/v8-chromium-release-0
Please CC v8-waterfall-sheriff@grotations.appspotmail.com on the revert to ensure that a human
is aware of the problem.

To file a bug in v8 10.6: https://bugs.chromium.org/p/v8/issues/entry
To file a bug in Chromium m106: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Bug: None
Tbr: v8-waterfall-sheriff@grotations.appspotmail.com
Change-Id: I4bd37e8816141a00b36d37c90fafc642fc4bb34e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3852518
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5249@{#79}
Cr-Branched-From: 4f7bea5-refs/heads/main@{#1036826}
blueboxd pushed a commit that referenced this issue Nov 30, 2022
Change-Id: Ib195ce7fa9cdf0f1fd7c195669a418cfcdb411e0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3963257
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5359@{#79}
Cr-Branched-From: 27d3765-refs/heads/main@{#1058933}
blueboxd pushed a commit that referenced this issue Feb 8, 2023
Despite the javadoc for JobService saying that it calls onStartJob() /
onStobJob() on the UI thread, we have evidence of the contrary.

Now uses a lock to tackle concurrency instead.

(cherry picked from commit fe8508a)

Bug: 1401509
Change-Id: I94e11d2fd8285ea9f480d99ba4af2494d61b276b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4114624
Reviewed-by: Sam Maier <smaier@chromium.org>
Reviewed-by: Mohamed Heikal <mheikal@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1084554}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4120780
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/branch-heads/5481@{#79}
Cr-Branched-From: 130f3e4-refs/heads/main@{#1084008}
blueboxd pushed a commit that referenced this issue Mar 7, 2023
Preview: https://crbug.com/1282157#c95

(cherry picked from commit 8cedfac)

Fixed: 1411421
Change-Id: I5050a190b2dd87f145ea61136a8f836ecdb42723
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4200244
Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: Gabriel Oliveira <gabolvr@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1098793}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4212528
Commit-Queue: David Roger <droger@chromium.org>
Auto-Submit: Gabriel Oliveira <gabolvr@google.com>
Cr-Commit-Position: refs/branch-heads/5563@{#79}
Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
blueboxd pushed a commit that referenced this issue Apr 14, 2023
(cherry picked from commit d831c17)

screenshot: https://drive.google.com/file/d/1PL7TuhXfXDwGUcsmXjVJMJXkT9lyt4uX/view?usp=sharing
Bug: 1418093
Change-Id: I2e314ff8393b450fa11024b33002f967918a6945
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4285037
Reviewed-by: Cathy Li <chili@chromium.org>
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1110579}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4298589
Reviewed-by: Krishna Govind <govind@chromium.org>
Owners-Override: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/branch-heads/5615@{#79}
Cr-Branched-From: 9c6408e-refs/heads/main@{#1109224}
blueboxd pushed a commit that referenced this issue May 9, 2023
Show sign-in only flow when flag kConsistencyNewAccountInterface is
enabled. Add metrics to it for better debug.

(cherry picked from commit f69ece7)

Bug: 1424934
Change-Id: I7aacbcbfcdc0da8f16da777aab06e1f49ae1e03d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4356324
Reviewed-by: Weilun Shi <sweilun@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Commit-Queue: Tina Wang <tinazwang@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1121544}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4376805
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/branch-heads/5672@{#79}
Cr-Branched-From: 5f2a724-refs/heads/main@{#1121455}
blueboxd pushed a commit that referenced this issue May 27, 2023
…14.0.5735.10-r1 to 114-5707.0-1682337030-benchmark-114.0.5735.11-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-arm-chromium-beta
Please CC c-compiler-chrome@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: c-compiler-chrome@google.com
Change-Id: I6bfbf0b2b430a20d9e36aed63fbf9aa62b187c61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4493219
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5735@{#79}
Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
blueboxd pushed a commit that referenced this issue Sep 10, 2023
This CL adds InitialServiceWorkerStatus histogram on navigation.

(cherry picked from commit c2f203f)

Bug: 1431792
Bug: 1471800
Change-Id: I34a12014f948a9fcbe3155fe687cfd76e651fc79
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4764965
Reviewed-by: Shunya Shishido <sisidovski@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Minoru Chikamune <chikamune@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1181363}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4778018
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/branch-heads/5938@{#79}
Cr-Branched-From: 2b50cb4-refs/heads/main@{#1181205}
blueboxd pushed a commit that referenced this issue May 16, 2024
IdentityManager#findExtendedAccountInfoByEmailAddress appears to be
returning a null CoreAccountInfo even when we know a CoreAccountInfo
for the email exists.

We already have the CoreAccountInfo, so no need to re-aquire it through
the email.

(cherry picked from commit 2586c20)

(cherry picked from commit f1d2eef)

Bug: 332900316
Change-Id: If4ab9bb2316ab3d6cdae4a8111581adb491ab2d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5458313
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Original-Original-Commit-Position: refs/heads/main@{#1288099}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5462333
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Original-Commit-Position: refs/branch-heads/6422@{#79}
Cr-Original-Branched-From: 9012208-refs/heads/main@{#1287751}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5468423
Cr-Commit-Position: refs/branch-heads/6367@{#934}
Cr-Branched-From: d158c6d-refs/heads/main@{#1274542}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants