New issue
Advanced search Search tips

Issue 782216 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Chrome performance comparison

Reported by ruch...@samsung.com, Nov 7 2017

Issue description

Steps to reproduce the problem:
1. Take two devices, for example Star(G965F) and Dream(G955F)/Huawei Mate 9 
2. Compare the chrome performance (reaction speed / execution speed / screen update / buckling / softness / speed of other App conversion)
3. Observe

What is the expected behavior?
Chrome performance in Star should be as good as in Dream/Huawei Mate 9.

What went wrong?
Chrome performance is worse in Star as compared to Dream/Huawei Mate 9.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 62.0.3202.84  Channel: n/a
OS Version: O OS
Flash Version:
 
Please find the logs.
dumpState_G965FXXU0AQK1_201711071629.zip
4.4 MB Download
dumpState_G955FXXU1AQJ5_201711071629.zip
4.0 MB Download
Components: Blink>PerformanceAPIs>NavigationTiming
Labels: Performance-Browser

Comment 4 by ricea@chromium.org, Dec 1 2017

Components: -Blink>PerformanceAPIs>NavigationTiming
I don't think this issue is related to the NavigationTiming API. I think the issue is that the performance is actually bad, not that the API that measures the performance is bad.

#1 I think this report is too general to be actionable by Chrome engineers. Is there a specific area where the browser is not performing as expected?
Status: WontFix (was: Unconfirmed)
***Bulk edit***

Closing due to inactivity, please feel free to reopen if needed.

Sign in to add a comment