Google Chrome 26 performance issue

7 posts, 0 answers
  1. Telerik Admin
    Telerik Admin avatar
    1572 posts
    Member since:
    Oct 2004

    Posted 09 Apr 2013 Link to this post


    Some of you already have noticed that their sites are working slower in Google Chrome since they have updated to version 26.

    We did some debugging and research and found out that the problem is in the browser itself and it is not caused by our controls in the pages. In short, if you have a quotation mark or an apostrophe inside input element in your page, and you do PostBack, the Chrome gets really slow when changing the innerHTML property of the DOM elements after the page loads again.

    The issue can be replicated using this sample code without using our controls:
    <asp:ScriptManager runat="server"></asp:ScriptManager>
    <asp:TextBox runat="server" ID="text1" Text="'"></asp:TextBox>
    <asp:Calendar runat="server"></asp:Calendar>
    <script type="text/javascript">
        function test()
            var start = (new Date()).getTime();
            var label = document.getElementById("<%= label1.ClientID%>");
            for (var i = 0 ; i < 10000 ; i++)
                label.innerHTML = i;
            var end = (new Date()).getTime();
            alert(end - start);
    <asp:Label runat="server" ID="label1"></asp:Label>
    <asp:Button runat="server" Text="Post Back" />
    <asp:Button runat="server" Text="Check Speed" OnClientClick="test(); return false;" />

    Simply run the code, click the Post Back button and then click Check Speed to see how much slower gets the execution of label.innerHTML = i;

    In the serialized Client State of our controls, we use JSON to serialize some properties of controls that they need to be persisted and send from client to server, for example: {"enabled":true,"emptyMessage":""} could be such string, it contains quotes and is kept inside hidden input in the page. So after the post back the innerHTML will get slower due to this bug in Chrome.
    Since in our code, there are a lot of places where innerHTML is used to change the content of an element(for example when navigating RadCalendar this is called around 30 times, one for each day of the month), you will experience some delay/lag when you do such client side operations.

    Note that this issue is happening even if you don't have inputs with quotes inside them, but in less degree. For example in Firefox the test function above works in 60ms and in Chrome in 80ms. After the PostBack, in Firefox continues to run in 60ms, but in Chrome it takes 9 seconds if there is input with quote, and 400ms if there is not. So in both cases there is problem in the Chrome.
    Also if you have more items in the DOM tree, the problem will be more visible. For example if you remove the asp:Calendar in the sample above, it will run much faster.

    We will continue to investigate if there is something that we can do, and we hope Google to fix the issue in their browser as soon as possible. If you have more information or any suggestions we will be glad to hear them.
  2. Gal
    Gal avatar
    48 posts
    Member since:
    Apr 2009

    Posted 09 Apr 2013 Link to this post

    Hi all 

    I found an additional problem in chrome V26 when using a standard LinkButton to post between pages it slowed the post an additional 13-14 seconds replacing the button to a RadButton with a ButtonType="LinkButton" resulted in a massive speed bust from 17s to 3s !!!
  3. Lloyd Phillips
    Lloyd  Phillips avatar
    29 posts
    Member since:
    Dec 2004

    Posted 09 Apr 2013 Link to this post

    Yes, we've experienced a major issue with Chrome and our application using jQuery. We're not using Telerik components but we've seen a difference of 2-3 seconds render times going up to 17 seconds.

    Not good.
  4. sergey
    sergey avatar
    1 posts
    Member since:
    Oct 2012

    Posted 10 Apr 2013 Link to this post

  5. EricLaw
    EricLaw avatar
    67 posts
    Member since:
    Oct 2012

    Posted 11 Apr 2013 Link to this post

    Google's working on this.
  6. Wendelstam
    Wendelstam avatar
    48 posts
    Member since:
    Feb 2006

    Posted 25 Apr 2013 Link to this post

    The issue has been resolved by the Chronium team, and it seems to be resolved in the latest Chrome Canary build 
    (Version 28.0.1488.0 canary) for me. Hopefully it wont be long until its resolved on the stable release as well.

  7. Wendelstam
    Wendelstam avatar
    48 posts
    Member since:
    Feb 2006

    Posted 11 Jul 2013 Link to this post

    In the stable channel release  28.0.1500.71 this has been fixed.
Back to Top