Status Update
No update yet.
Comments
ka...@gmail.com
Project: platform/frameworks/support
Branch: androidx-main
Author: Radha Nakade <
Link:
Migrate traffic from pixel2 to mediumphone on FTL emulators.
Expand for full commit details
Migrate traffic from pixel2 to mediumphone on FTL emulators.
Bug: 396715333
Test: ./gradlew emoji2:emoji2-emojipicker:ftlmediumphoneapi33
Change-Id: If5555443ca1a91479128e1bd6f4f909154c40ba2
Files:
- M
buildSrc/private/src/main/kotlin/androidx/build/FtlRunner.kt
Hash: c76f8094154101867327912e659ae47509755957
Date: Wed Feb 26 11:27:46 2025
ka...@gmail.com
- This is not a duplicate.
- You have not given me the permission to UN-duplicate. Please UN-duplicate this ticket.
- Additionally, you have not provided any update of your testing and whether you are able to confirm this is an issue and what are you doing about this issue that the entire world is facing?
Please provide an update on the resolution of this ticket,
I have provided all the steps to reproduce the issue and I would like you to resolve this ASAP please.
- You have not given me the permission to UN-duplicate. Please UN-duplicate this ticket.
- Additionally, you have not provided any update of your testing and whether you are able to confirm this is an issue and what are you doing about this issue that the entire world is facing?
Please provide an update on the resolution of this ticket,
I have provided all the steps to reproduce the issue and I would like you to resolve this ASAP please.
Description
Steps to reproduce the problem
After this if you do not experience serious lagging behavior on interaction then contact me, cause many users are complaining of this since 1 year, I will happily screenshare with you and collect logs for you too.
I am a developer myself and have sent you bug reports many times since the last 1 year i am experiencing this issue and have switched to Firefox because of Chrome developers not doing anything on my bug reports. I hope this time it is picked up and the problem is fixed once and for all.
Please contact me if you cannot reproduce instead of blatantly updating ticket saying "cannot reproduce"
Problem Description
Serious lagging in Chrome browser when you open sites that use heavy JavaScript and in memory object arrays. Either this is due to a memory, energy saving feature you introduced or just some inherent update done.
This is a complaint from one of the users from -https://support.google.com/chrome/thread/253559090/chrome-has-suddenly-become-very-slow?hl=en :
"After update to the 120.0.6099.217 version, the chrome becomes very slow, eats much more gigs of RAM and very often the whole GUI freeze for many seconds, especially when I use go back but it happens in other situation too, usually when I want to load another page, doesn't matter how - by entering address manually, paste it from clipboard or just by click to hyperlink. Very often also shortcut CTRL+N or CTRL+T simply doesn't work for a while or it takes many seconds before new window or tab appears. Current version of Microsoft Edge is now much much much faster then Chrome even with hundreds of tabs but in reality is still on same speed, just Chrome is now super slow and laggy."
Additional Comments
Chrome Variations uploaded a attachment.
Even your report a bug section is laggy making is hard to report bugs
Summary
Whole world is experiencing serious lagging problems but you simply reply by saying cannot reproduce
Additional Data
Category: UI
Chrome Channel: Stable
Regression: Yes