New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 662312 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

content_shell on windows taking significant amount of time for loading

Project Member Reported by vivekg@chromium.org, Nov 4 2016

Issue description

Version: 56.0.2909.0
OS: Windows 7
Commit Id: a31176dcb88ec9e9464be15a65e154cd0e3f368b

Pre-requisite:
    Create a directory e.g. C:\test and place the following index.html file in it.

    index.html
    ==========
    <h1>Hello World</h1> 

    From within this C:\test directory run `python -m SimpleHTTPServer 80`

What steps will reproduce the problem?
(1) Build content_shell and chrome targets on Windows
(2) Launch content_shell as
out\content_shell http://localhost --trace-startup --trace-startup-duration=10 --trace-startup-file=content_shell_trace.json

(3) Launch chrome as
out\chrome http://localhost --trace-startup --trace-startup-duration=10 --trace-startup-file=chrome_trace.json

What is the expected output?
The loading time should be same either on chrome or content_shell

What do you see instead?
Load time on content_shell is significantly high

Please use labels and text to provide additional information.
Attaching trace files generated from both chrome and content_shell.
 
chrome_trace.json
3.8 MB View Download
content_shell_trace.json
1.5 MB View Download
Cc: kphanee@chromium.org
Labels: -Performance -Performance-Startup Performance-Loading
Status: Available (was: Untriaged)
Project Member

Comment 3 by sheriffbot@chromium.org, Apr 27 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
Triage: WontFixing due to inactivity. Feel free to reopen if there's more data.

Sign in to add a comment