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

Issue 648085 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

GXT Form with Tree component doesn't working in Chrome 53 on Windows

Reported by anton.fo...@gmail.com, Sep 18 2016

Issue description

Chrome Version       : 53.0.2785.116 (Официальная сборка) m (64 бит)
URLs (if applicable) : https://demo.dentplan.ru/?login=ddf1bba6302d01188073&section=expenditures
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: OK
    Firefox: OK
         IE: OK

What steps will reproduce the problem?
The demo version (wich not requires any registration) of our GXT-based application contains the form which causes the problem.
(1) Visit our website www.dentplan.ru.
(2) Click the orange button to start demo application (as shown in attached file). Every orange button opens one corresponding form after demo loaded, the 4-th button (located in "Контроль расходов" section) opens the form what causes a problem.
(3) You can open any form in demo application, but only "Расходы" form, which contains Tree component, causes a problem (as shown in attached file).

What is the expected result?
The form should open.

What happens instead?
Web application immediately and totally stops to responding.

Additional information:
The bug appeared when Chrome was updated to version 53.0.2785.101. The problem occurs only on Windows (all versions, I tried in 10, 7, Server 2008). In MacOS and iOS all works correctly.
Our web application uses Sencha GXT 2.3.1a and GWT 2.7.0. Bug appears in every form with Tree component. All other forms are working properly. When you tried to open a form with tree, page immediately stops to responding. After a little time a Chrome's standard dialog "Page not responding" is appearing. If a developer tools panel was open before, no activity displayed in it. After the effect happened, it become not easy to close tab in the top bar of Chrome.
 
screen01.jpg
198 KB View Download
screen02.jpg
62.1 KB View Download
screen03.jpg
225 KB View Download
Cc: krajshree@chromium.org
Labels: -Type-Bug -Pri-3 hasbisect-per-revison M-53 OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: mattcary@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 10 and Ubuntu 14.04 using reported version #53.0.2785.116 and latest canary #55.0.2864.0.

Bisect Information:
=====================
Good build: 53.0.2754.0
Bad Build : 53.0.2756.0

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/1a3db4d18d2d8c243da9a7e4b8c30c709dbbf352..65c873e2440233e3b12242930190869a5fd90919

From the above change log suspecting below change

Review URL:  https://codereview.chromium.org/2023073003

mattcary@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.
Cc: mattcary@chromium.org szager@chromium.org
Owner: ----
My change was for internal performance utilities that are not part of the chrome build.

+szager@, it looks like your change in the referenced log is in the only thing that might be plausible, could you take a look?
Components: Blink>Forms>Url

Comment 4 by tkent@chromium.org, Sep 20 2016

Components: -Blink>Forms>Url Blink
Labels: Needs-Reduction
Status: Untriaged (was: Assigned)
Labels: -hasbisect-per-revison hasbisect-per-revision
Fixing the spelling error in label.
Components: -Blink Blink>Layout

Comment 7 by drott@chromium.org, Oct 3 2016

Status: Needs-Feedback (was: Untriaged)
The original content is not accessible any more, it seems to give an error about not being logged in. Can you please provide a new URL for reproducing the problem?

Comment 8 by drott@chromium.org, Oct 3 2016

Labels: -Pri-1 Pri-2
Hello!
Today I updated my Chrome browser to version 53.0.2785.143 m (64-bit), and problem is gone! I tried to reproduce error on Windows and MacOS, and all working fine.
It's very good, but it's also strange, because there are no comments here about fix for this error.
To reproduce error in older version mentioned earlier, please perform steps described in section "What steps will reproduce the problem?" (and see attached screenshots). Error may not be reproduced by direct link.

Comment 10 by e...@chromium.org, Jan 27 2017

Status: Fixed (was: Needs-Feedback)
Thanks for the confirmation.

Sign in to add a comment