Closed
Bug 1277159
Opened 8 years ago
Closed 8 years ago
[Perf][google docs] Firefox slower than Chrome 1.05%(1656 ms) when running gdoc_create_isolate_image_10
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
platform-rel | --- | ? |
People
(Reporter: fatseng, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [platform-rel-Google][platform-rel-GoogleDocs])
No description provided.
Reporter | ||
Updated•8 years ago
|
Blocks: Meta-Hasal-GDoc
Reporter | ||
Updated•8 years ago
|
Summary: Firefox slower than Chrome 1.05%(1656 ms) when running gdoc_create_isolate_image_10 → [Perf][google docs] Firefox slower than Chrome 1.05%(1656 ms) when running gdoc_create_isolate_image_10
Reporter | ||
Comment 1•8 years ago
|
||
# Test Case
STR
1. Launch the browser with blank page
2. input the blank google doc page url
3. insert 1 image
4. repeat step 3, 10 times
5. close the browser
Test Scripts:
https://github.com/Mozilla-TWQA/Hasal/blob/master/tests/test_chrome_gdoc_create_isolate_image_10.sikuli/test_chrome_gdoc_create_isolate_image_10.py
https://github.com/Mozilla-TWQA/Hasal/blob/master/tests/test_firefox_gdoc_create_isolate_image_10.sikuli/test_firefox_gdoc_create_isolate_image_10.py
# Hardware
OS: Ubuntu 14.04 LTS 64-bit
CPU: i7-3770 3.4GMhz
Memory: 16GB Ram
Hard Drive: 1TB SATA HDD
Graphics: GK107 [GeForce GT 640]/ GF108 [GeForce GT 440/630]
# Browsers
Firefox version: 45.0.2
Chrome version: 50.0.2661.86
# Result
Browser | Run time (median value) (ms)
Firefox | 159122.222
Chrome | 157466.667
Updated•8 years ago
|
Whiteboard: [platform-rel-Google][platform-rel-GoogleDocs]
Updated•8 years ago
|
platform-rel: --- → ?
Comment 2•8 years ago
|
||
Mark as minor case, and marked wontfix in this iteration. Revisit here if necessary.
This bug fixing iteration will focus on critical bug 1264535, bug 1269666, bug 1269684, bug 1269690, bug 1269695, bug 1269698.
Severity: normal → minor
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•