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

Issue 698717 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: ----
Hotlist-MemoryInfra



Sign in to add a comment

Doodle de hoy 06/03/2017

Reported by victor.c...@gmail.com, Mar 6 2017

Issue description

Chrome Version: 56.0.2924.87
OS: Windows 7 SP1
url: https:\\www.google.es

Buenos días, he apreciado hoy, que al abrir la url https:\\www.google.es, se observa en el administrador de tareas de google chrome, que el proceso de GPU, empieza a dispararse llegando al consumo de 530 megas de memoria rápidamente.

El problema ocurre aunque no se llegue a reproducir el doodle, es posible que haya algún tipo de falla en la inclusión del código de dicho doodle. Es posible que ordenadores que no dispongan de memoria suficiente llegaran a presentar problemas de rendimiento.

Por desgracia se soluciona cerrando la url https:\\www.google.es

Un Saludo.
 
He podido comprobar que sólo está ocurriendo en la versión de 32 bits.

También he probado a abrir la url https:\\www.google.es en más de una ocasión y al mantenerlas abiertas, el consumo de se multiplica según las veces que abras dicha url (por ejemplo tras tener dos pestañas con la url se ha duplicado el consumo).
Labels: Needs-Triage-M56
Cc: kavvaru@chromium.org
Components: UI>Browser>Search
Labels: Needs-Feedback
Unable to reproduce the issue on Windows 7 using chrome version 56.0.2924.87.
Not observed any memory increase in task manager with URL  https:\\www.google.es.

victor.cardenas.berlanga@ Could you please confirm are you still facing this issue ?Please provide us any screen cast for better understanding the issue.

Thanks, 
Components: -UI>Browser>Search Platform>DevTools>Memory
If there is an issue here, it would be with some kind of general Blink memory use, not with search-in-omnibox.  I'm not sure which component is right for that.  Hopefully I got closer to someone who knows.
Buenos días, tras una serie de pruebas he vuelto a poder reproducir el problema, y puedo decir a ciencia cierta que el problema de consumo esta asociado con el doodle (37 aniversario de dragón de komodo).

He podido reproducirlo buscando en el historico de doodles en la url:

https://www.google.com/doodles/37th-anniversary-of-komodo-national-park

Adjunto unos pantallazos con el consumo aumentado al abrir una vez la url, o duplicado si se abre dos veces.

Un saludo.
sin_consumo.png
77.3 KB View Download
consumo_1.png
224 KB View Download
consumo_2.png
218 KB View Download
Project Member

Comment 6 by sheriffbot@chromium.org, Mar 9 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: krajshree@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Win-7 and Win-10 using chrome reported version #56.0.2924.87 and latest canary #59.0.3036.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Navigated to URL; Https://www.google.com/doodles/37th-anniversary-of-komodo-national-park
2. Pressed shift + ESC to open task manager.
3. Observed that the GPU process memory did not increase and remained at 80 to 90 MB.

victor.cardenas.berlanga@ - Could you please check this issue on latest canary #59.0.3036.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
698717.mp4
4.8 MB View Download
Components: -Platform>DevTools>Memory Internals>Instrumentation>Memory
I think the instrumentation team may be a better start for a group to put this through more. As far as I can tell nothing with this report is related to the DevTools memory analysis data but the Task Manager's reported memory usage of a site.
Buenos días, he probado hoy con la versión 57.0.2987.98, tanto en perfil limpio como me dijo el compañero, como en mi perfil habitual, y parece que ya está solventado el problema en esa versión, gracias y un saludo.
Project Member

Comment 10 by sheriffbot@chromium.org, Mar 15 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: rbasuvula@chromium.org
Labels: -Needs-Triage-M56
Status: WontFix (was: Unconfirmed)
Mark it as WontFix as per comment#9 feedback provided by reporter(Good morning, I tried today with version 57.0.2987.98, both in clean profile as the companion told me, as in my usual profile, and it seems that the problem is solved in that version, thanks and greetings).
Feel free to raise a new issue if sill facing.

Thank you!

Sign in to add a comment