[GIS] ExtJS 4.2 layout crush on latest chrome but not on old one in full screen

Question

I've noticed that only in chrome my GeoExt app crush when I open many layers.
If I resize the window , the layout seems to look good , once I resize to bigger screen , it mess again.

The app code didn't change for long time , it doesn't happen on old laptop with chrome version 27 it only happens on 2 stronger desktops with latest chrome version.

UPDATE

I've found out that commenting the following CSS in openlayers resolve the problem , Any idea why ?

  /**
 * Animations
 */

      .olLayerGrid .olTileImage {
        /*-webkit-transition: opacity 0.2s linear;*/
        -moz-transition: opacity 0.2s linear;
        -o-transition: opacity 0.2s linear;
        /*transition: opacity 0.2s linear;*/
    }

    /* Turn on GPU support where available */
    .olTileImage {
        /*-webkit-transform: translateZ(0);*/
        -moz-transform: translateZ(0);
        -o-transform: translateZ(0);
        -ms-transform: translateZ(0);
        /*transform: translateZ(0);*/
        /*-webkit-backface-visibility: hidden;*/
        -moz-backface-visibility: hidden;
        -ms-backface-visibility: hidden;
        backface-visibility: hidden;
        -webkit-perspective: 1000;
        -moz-perspective: 1000;
        -ms-perspective: 1000;
        perspective: 1000;
    }

Answer 1

It seems there are old and constant stability problems when running ExtJS applications based, on Chrome:

• the latest Chrome crashes on animation in ExtJs 4 charts and draws them incorrectly
• ExtJS 4.2.1 calendar demo in sencha.com crashes in chrome

These problems have been reported to Sencha and Google:

• SVG Rendering issue with Highcharts charting library

In time, there were new Chrome and ExtJS versions, which brought some improvements:

• Ext JS 4.2.1 GA is Now Available!

Unfortunately, again, some users have reported errors:

• App is undefined in Chrome version 28

In this situation, I think you need to test the latest Chrome with different ExtJS versions (like 4.2.1, 4.2.2 or newer revisions) and hope your application isn't affected by the latest incompatibility.